Cannot read property 'loaders' of undefined about grunt-webpack HOT 10 CLOSED

ya, adding

module: {
    loaders: []
}

at the same level as entry/output/etc did the trick, as is somewhat reasonable. thx

from grunt-webpack.

I had same error when I was using jade-loaders

        loaders: [
          test: /\.jade$/,
          loader: 'jade-loader'
        ]

I just downgraded to version 1.0.8 where it worked just fine.

from grunt-webpack.

@cdaringe @mareksimunek looks like there was a reference to options.module.loaders added in 6ab5ea1, after the 1.0.8 tag. When I push a new tag out recently, it picked up that change set as well.

@roddeh @sokra Any thoughts on a fix? Seems like a simple check for options.module might do the trick, I'm just not 100% sure what that changeset is doing and if there is anything else needed.

from grunt-webpack.

What is options.module used for? It's undocumented.

from grunt-webpack.

@jakiestfu I believe options in this context is simply the webpack config, in which case module is simply this: http://webpack.github.io/docs/configuration.html#module-loaders

from grunt-webpack.

@jakiestfu possibly helpful: https://github.com/webpack/webpack-with-common-libs/blob/master/Gruntfile.js - which includes:

var webpackConfig = require("./webpack.config.js");
    grunt.initConfig({
        webpack: {
            options: webpackConfig,
                        ....

Where options: webpackConfig is simply the required webpack config object that has module.loaders

from grunt-webpack.

Needing to set an empty list in config feels like a workaround to a bug to me. The patch (linked) should prevent the need to do that.

from grunt-webpack.

looks good

from grunt-webpack.

This code should be more defensive?

https://github.com/webpack/grunt-webpack/blob/master/tasks/webpack.js#L44

Should check if the "options.module" exist before checking "options.module.loaders"?

from grunt-webpack.

@almandsky @cdaringe closed with #44 - thanks @muffinresearch 🎉

from grunt-webpack.