Setup via `webpack.config.js` file not working with NamedModulesPlugin about expose-loader

[ypconstante]

There is any progress to fix this bug? I'm trying to migrate a project to webpack and I spent some hours trying to figure out what I was doing wrong and in the end it was this incompatibility between NamedModulesPlugin and expose-loader.

[sokra]

That's a bug in libIdent webpack/webpack.

[WiseBird]

@sokra Should I refile it there?

[ypconstante]

Some other issues related this bug:

• webpack/webpack#4613
• #49
• webpack-contrib/extract-text-webpack-plugin#648

The extract-text-webpack-plugin issue was fixed, maybe the fix is similar.

[cansin]

I tried to look at how extract-text-webpack-plugin got fixed to understand whether a similar pattern can be applied to expose-loader. But honestly, I have no idea. I hope someone that is familiar with either can send a patch PR soon.

[cansin]

Actually the problem expose-loader encountering might be different from what extract-text-webpack-plugin is having (based on webpack-contrib/extract-text-webpack-plugin#648 (comment) ).

[cansin]

So a patch to webpack/webpack (as described at webpack/webpack#4613 (comment) ) "fixes" this issue. But I think such a patch would also mess up with the consistent hashing for long-term caching since for the modules skipped hashing would be non-deterministic (I think). But I am not sure. I am hoping @sokra would weigh in.

[timse]

just saw this after opening #58 sorry for that :P.

The issue probably should be handled by webpack?

probably modules created in the pitch phase should by default get a new userRequest

[cansin]

@timse thanks for #58 ! That would at least unblock everyone while the underlying issue gets fixed at https://github.com/webpack/webpack .

[adrielwerlich]

Module build failed: TypeError: this.query.substr is not a function
at Object.module.exports.pitch (...\node_modules\expose-loader\index.js:43:34)

What about this message?