Leo Jiang
Reputation: 26213
How do I find out which module caused an error in Webpack?
When I run webpack, I get ERROR in Cannot find module 'lodash/lang/isFunction'. However, multiple module depend on lodash. How do I make Webpack go into debug or verbose mode?
Adding debug: true in my Webpack config file didn't do anything.
Upvotes: 0
Views: 712
Answers (1)
Brendan Gannon
Reputation: 2652
Are you familiar with the --display-error-details flag? Setting this when executing a build gives you more verbose output on errors (e.g. when a module is missing it will show you all the places it looked to find it). As far as I can tell this is command line only; I haven't been able to find an equivalent when running webpack via node.
Upvotes: 1
Related Questions
- Field 'browser' doesn't contain a valid alias configuration
- How to fix npm throwing error without sudo
- Error: Cannot find module 'webpack-cli/bin/config-yargs'
- Error: Cannot find module 'webpack'
- Cannot find module 'path'
- NPM global install "cannot find module"
- How to fix : Cannot find module 'webpack/bin/config-yargs'
- webpack error in Cannot find module 'less'
- Cannot find module 'webpack-cli/bin/config-yargs', cannot find module 'webpack-cli'
- Error: Cannot find module 'stylelint' Webpack