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.
Module not found: Error: Can't resolve 'module' in '...'
See original GitHub issueDo you want to request a feature or report a bug? bug
What is the current behavior?
const module = require('module')
// Module not found: Error: Can't resolve 'module' in '...'
This line of code throws on error even in “node” target
If the current behavior is a bug, please provide the steps to reproduce.
just requiring the module module will cause the issue.
What is the expected behavior?
module is a native module in node, just like fs or http, webpack should not throw when its required.
If this is a feature request, what is motivation or use case for changing the behavior?
I need to use the module module!
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
latest webpack version, nodeJS 8.1.3, mac OSX
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Any updates here?
Getting this error:
Module not found: Can’t resolve ‘module’ in ‘project_root\node_modules\load-grunt-tasks\node_modules\resolve-from’
@sokra can you elaborate on the reason?