babel-plugin-webpack-aliases

This is a fork of babel-plugin-webpack-alias

This Babel 6 plugin allows you to use webpack aliases in Babel.

This plugin is simply going to take the aliases defined in your webpack config and replace require paths. It is especially useful when you rely on webpack aliases to keep require paths nicer (and sometimes more consistent depending on your project configuration) but you can't use webpack in a context, for example for unit testing.

Example

With the following webpack.config.js:

``js
module.exports = {
...
resolve: {
alias: {
'my-alias': path.join(__dirname, '/alias-folder/js/'),
'library-name': './library-folder/folder'
}
}
...
};
`

A javascript file before compilation:

`js
var MyModule = require('my-alias/src/lib/MyModule');
import MyImport from 'library-name/lib/import/MyImport';
`

will become:

`js
var MyModule = require('../../alias-folder/js/lib/MyModule');
import MyImport from '../../library-folder/folder/lib/import/MyImport';
`

This is an example but the plugin will output the relative path depending on the position of the file and the alias folder.

Install

`shell
npm install --save-dev babel-plugin-webpack-aliases
`

Add it as a plugin to your .babelrc file. You can optionally add a path to a config file, for example:

`json
{
"presets":[ "react", "es2015", "stage-0" ],
"env": {
"test": {
"plugins": [
[ "babel-plugin-webpack-aliases", { "config": "./webpack.config.test.js" } ]
]
}
}
}
`

In this case, the plugin will only be run when NODE_ENV is set to test.

It is also possible to pass a findConfig option, and the plugin will attempt to find the nearest configuration file within the project using find-up. For example:

`json
{
"presets":[ "react", "es2015", "stage-0" ],
"env": {
"test": {
"plugins": [
[ "babel-plugin-webpack-aliases", {
"config": "webpack.config.test.js",
"findConfig": true
} ]
]
}
}
}
``