Improved log in console

[evenstensberg]

I was having this issue when setting up webpack 2.0 with ES6 and arrow functions. I had no idea that I removed a bracket when deleting one of my plugins and it threw an odd error. I didn't know what the case was and used a lot of time trying to figure out what went wrong. This could potentially help a lot of developers to get a clue what went wrong when transpiling webpack.config with babel through renaming (webpack.babel.config.js)

[gajus]

Can you provide a code example that broke and triggered this error?

[evenstensberg]

const {resolve} = require('path')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const webpack = require('webpack')

const isProd = process.env.NODE_ENV === 'production'
const isTest = process.env.NODE_ENV === 'test'

module.exports = env => {
  return {
    entry: {
      app: './app.js',
    },
    output: {
      filename: 'bundle[name].js',
      path: resolve(__dirname, 'dist'),
      pathinfo: !env.prod,
    },
    context: resolve(__dirname, 'scr'),
    devtool: env.prod ? 'source-map' : 'eval',
    bail: env.prod,
    module: {
      loaders: [
        {test: /\.js$/, loader: 'babel!eslint', exclude: /node_modules/}
      ]
    },
    plugins: [
      env.test ? undefined : new HtmlWebpackPlugin({
        template: './index.html'
      }),

      env.test ? undefined : new webpack.optimize.CommonsChunkPlugin({
        name: 'common',
        filename: 'bundle.common.js'
      })
    ]
}

[gajus]

How would a missing bracket in this code cause

Cannot remove "babel-plugin-transform-es2015-modules-commonjs" from the plugin list.

error?

[evenstensberg]

I'm transpiling the config through babel first 😄 ( webpack 2.0)

[matt-mcdaniel]

I currently have an issue open for receiving the same error. In my case, this warning would not be helpful, as there are no syntax errors in my webpack file.

[evenstensberg]

Probably should add up that you need to check loaders or babel file too, but that seems a bit volatile to me

[matt-mcdaniel]

Alternatively, the error itself could be made to be more accurate.

[evenstensberg]

Generally something is wrong in your config file if you forgot a plugin :)