Closed nfriend closed 7 years ago
After doing a little bit of debugging, I think this actually an issue with how I'm using webpack-stream
- I seem to be inadvertently suppressing warnings. I'll close this issue for now and reopen later if necessary.
Yep, the issue was with webpack-stream
. If anyone else is having this issue and is using webpack-stream
, check out this comment for an example of how to manually log errors and warnings: https://github.com/shama/webpack-stream/issues/64#issuecomment-207373677
Thanks for the follow up @nfriend.
Perhaps I'm just using this plugin wrong, but I can't seem to get any output even when I know my build contains multiple versions of the same module. For example, I made a quick test app that has the following dependency structure:
When I run the app, this is the output:
As you can see, the modules and the app are all reporting that they are using different versions of
lodash
. However, my build output doesn't show any warnings:Just to show that the app is correctly reporting the
lodash
versions, if I add the following alias in my app'swebpack.config
:the app displays this:
Just to be complete, here's my full
webpack.config.js
:I use this
webpack.config.js
in my gulp build, where Irequire()
the file and pass it towebpack-stream
to perform the actual webpack build.Any ideas? Is there something else I need to do to make this plugin warn me when I use multiple versions of
lodash
? Thanks!