Can't use storybook ^2.0.0 when babel-loader is defined in preLoaders

Hi!

My webpack configuration is something like this:

{
  entry: {...},
  output: {...},
  module: {
    noParse: [/moment.js/],
    loaders: [
      { test: /\.json$/, loaders: ['json'] },
      { test: /\.scss$/, loaders: [ 'style', 'css', 'postcss', 'sass' ] },
      { test: /\.css$/, loaders: [ 'style', 'css?-minimize', 'postcss' ] },
      { test: /\.(ttf|eot|otf)(\?v=[0-9]\.[0-9]\.[0-9])?$/, loaders: [ 'file?name=[name].[ext]' ] },
      { test: /\.svg$/, loaders: [ 'file?name=[name].[ext]', 'svg-process' ] },
    ],
    preLoaders: [
      {
        test: /\.js$/,
        loader: 'rebem-layers',
        exclude: /node_modules/,
      },
      {
        test: /\.js$/,
        exclude: /node_modules/,
        loader: 'babel-loader',
        query: {
          cacheDirectory: true,
          env: {
            development: {
              presets: [ 'react-hmre' ],
            },
          },
        },
      },
      {
        test: /\.js$/,
        loader: 'eslint-loader',
        exclude: /node_modules/,
      },
    ],
  },

The problem is as I see is, that storybook 2.0.0 defines the new default webpack config. There a default babel-loader is probably defined, and my configuration is not overriding that. I am assuming this also from the fact, that running storybook is now very slow and it shows that babel is trying to transpile everything from node_modules (which is excluded in my configuration).

Reverting to storybook 1.41.0 version was my temporary solution.

[PTihomir]

Sorry about the wrong path 😃 I was checking if some of the stories affect the whole picture, and after that I forgot to revert.

I will try the newer version on our full project.

[arunoda]

Great. Awesome.