babel-plugin-resolver - npm Package Compare versions

Comparing version 0.0.4 to 0.0.5

lib/ResolverPlugin.js

History.md


		v0.0.5 / 2016-01-05
		==================

		* v0.0.5
		* rename main to ResolverPlugin
		* Merge pull request #1 from iuriikozuliak/patch-1
		* Update getPluginOptsFromBabelOpts.js
		* tweak copy
		* v0.0.4

		v0.0.4 / 2015-11-21
		@@ -3,0 +13,0 @@ ===================

lib/getPluginOptsFromBabelOpts.js

		@@ -7,3 +7,3 @@ var _ = require('lodash');
		module.exports = function getPluginOptsFromBabelOpts(babelOpts) {
		var plugin = _.findWhere(babelOpts.plugins, function (plugin) {
		var plugin = _.find(babelOpts.plugins, function (plugin) {
		// hack: assume it's the correct plugin if it's options have a `resolveDirs` property
		@@ -10,0 +10,0 @@ return _.isArray(plugin) &&

package.json

		{
		"name": "babel-plugin-resolver",
		"version": "0.0.4",
		"version": "0.0.5",
		"description": "Resolve modules from any directory.",
		"main": "lib/index.js",
		"main": "lib/ResolverPlugin.js",
		"scripts": {
		@@ -7,0 +7,0 @@ "test": "npm run clear-cache && npm run lint && node_modules/.bin/mocha test/*/.test.js",

Readme.md

		@@ -99,5 +99,3 @@ # Babel Resolver Plugin [![NPM version][npm-image]][npm-url] [![Build status][travis-image]][travis-url]

		While setting `NODE_PATH=app` is a perfectly valid solution, `babel-plugin-resolver` is for those who:
		- find environment variables annoying
		- want to resolve modules from more than one directory
		While setting `NODE_PATH=app` is a perfectly valid solution, `babel-resolver` is more explicit and lets you avoid mucking around with environment variables.

		@@ -104,0 +102,0 @@ ## License

lib/index.js

New alerts