New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup via webpack.config.js
file not working with NamedModulesPlugin
#55
Comments
That's a bug in |
@sokra Should I refile it there? |
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. |
Some other issues related this bug:
The extract-text-webpack-plugin issue was fixed, maybe the fix is similar. |
I tried to look at how |
Actually the problem |
So a patch to |
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 |
@timse thanks for #58 ! That would at least unblock everyone while the underlying issue gets fixed at https://github.com/webpack/webpack . |
Module build failed: TypeError: this.query.substr is not a function What about this message? |
Reproduction - https://github.com/WiseBird/expose_loader_named_modules_plugin
I use
expose-loader
to expose jquery:It works without
NamedModulesPlugin
while producing next output:when
NamedModulesPlugin
is included output is following:So both modules: the one exposing jquery and the one containing jquery have the same name.
Moreover when exposing via
require('expose-loader?jQuery!jquery');
the module exposing jquery have different name:NamedModulesPlugin
useslibIdent
fromNormalModule
that in its order usesuserRequest
that differs when library exposed via config file or via require statement.The text was updated successfully, but these errors were encountered: