Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Webpack error when using the module
See original GitHub issueHi. I cannot get my application built when using redux-auth, always get an error like that:
WARNING in ./~/encoding/lib/iconv-loader.js
Critical dependencies:
9:12-34 the request of a dependency is an expression
@ ./~/encoding/lib/iconv-loader.js 9:12-34
This is my webpack config: https://gist.github.com/varya/bfab41797d00242a08e1
Could you give any suggestion?
Issue Analytics
- State:
- Created 8 years ago
- Reactions:8
- Comments:13 (1 by maintainers)
Top Results From Across the Web
webpack: Module not found: Error: Can't resolve (with relative ...
Your file structure says that folder name is Container with a capital C. But you are trying to import it by container with...
Read more >How I solved and debugged my Webpack issue through trial ...
When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.
Read more >"0:0 error Module Error [...]" when using with webpack #1909
It seems there is a bug when using webpack --mode development ... assets/javascripts/blocks/Search.es6 21:37 error Module Error (from .
Read more >How to fix Error: cannot find module "webpack" - Educative.io
The Cannot find module webpack occurs when webpack is not globally installed. It is a problem with the npm script or application. You...
Read more >Modules - webpack
webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I updated from 0.2.0 to 0.0.5-beta5 and now no longer need to have this exclusion in my webpack config
new webpack.NormalModuleReplacementPlugin(/\/iconv-loader$/, 'node-noop')My bundle size is also a lot smaller, no more references to node-fetch/iconv-lite/encodings
@steelx fetching latest version from github instead of npm solved this issue for me