I'm developing a web app at work in React/Redux/Webpack and am now starting to integrate testing with Mocha.
I followed the instructions for writing tests in the Redux documentation, but now I have run into an issue with my webpack aliases.
For example, take a look at the imports section of this test for one of my action creators:
import expect from 'expect' // resolves without an issue
import * as actions from 'actions/app'; // can't resolve this alias
import * as types from 'constants/actionTypes'; // can't resolve this alias
describe('Actions', () => {
describe('app',() => {
it('should create an action with a successful connection', () => {
const host = '***************',
port = ****,
db = '******',
user = '*********',
pass = '******';
const action = actions.createConnection(host, port, db, user, pass);
const expectedAction = {
type: types.CREATE_CONNECTION,
status: 'success',
payload: { host, port, database, username }
};
expect(action).toEqual(expectedAction);
});
});
});
As the comments suggest, mocha isn't able to resolve my import statements when they are referencing aliased dependencies.
Because I'm still new to webpack, here's my webpack.config.js
:
module.exports = {
devtool: 'eval-source-map',
entry: [
'webpack-hot-middleware/client',
'./src/index'
],
output: {
path: path.join(__dirname, 'dist'),
filename: 'bundle.js',
publicPath: '/static/'
},
resolve: {
extensions : ['', '.js', '.jsx'],
alias: {
actions: path.resolve(__dirname, 'src', 'actions'),
constants: path.resolve(__dirname, 'src', 'constants'),
/* more aliases */
}
},
plugins: [
new webpack.optimize.OccurenceOrderPlugin(),
new webpack.HotModuleReplacementPlugin(),
new webpack.NoErrorsPlugin()
],
module: {
loaders: [{
test: /\.js$/,
loaders: ['babel'],
exclude: /node_modules/,
include: __dirname
}]
}
};
Also, I'm using the command npm test
to run mocha, here's the script I'm using in my package.json
.
{
"scripts": {
"test": "mocha ./src/**/test/spec.js --compilers js:babel-core/register --recursive"
}
}
So here's where I get stuck. I need to include the aliases from webpack into mocha when it runs.
I also encountered the same problem, but with this plugin I solved it.
https://www.npmjs.com/package/babel-plugin-webpack-aliases
The execution command of your "mocha" is not reading the
webpack.config.js
, so it can not resolve the alias.By setting this plugin, consider
webpack.config.js
when compiling with "babel-core/register". As a result, the alias will also be valid during testing.and add this setting to
.babelrc
You can also use a babel plugin I authored: https://github.com/trayio/babel-plugin-webpack-alias It will convert your aliased path to relative paths just by including a babel plugin to your
.babelrc
.