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.
Module not found: Can't resolve 'child_process'
See original GitHub issueIn development mode, with v3.0.2
I’m getting this issue :
error - ./node_modules/esbuild/lib/main.js:1535:0
Module not found: Can't resolve 'child_process'
Someone ever got this one ?
Issue Analytics
- State:
- Created 2 years ago
- Comments:10
Top Results From Across the Web
Module not found: Error can't resolve 'child_process', how to fix?
But as soon as I try to use child process, using 'require("child_process")' I get the following error when trying to build the extension....
Read more >Module not found: Can't resolve 'child_process' error [Solved]
The error "Module not found: Error: Can't resolve 'child_process'" occurs because there has been a breaking change in Webpack version 5. To solve...
Read more >Module not found: Can't resolve 'child_process' #192 - GitHub
error whenever I try to use node-notifier. I'm using Node v6.11.2 and the code is copy-paste from the examples. Any ideas?
Read more >Module not found: Error can't resolve in react - YouTube
The following issues are handled:1. Module not found : Error can't resolve ' child_process '2. Uncaught ReferenceError: the process is not ...
Read more >Can't Resolve "child_process" in module xmlhttprequest-node.js
It appears if you are trying to use the xmlhttprequest package on the front end. Since the xmlhttprequest package only works on NodeJS,...
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
Ah good find, thanks for digging deeper and finding the fix! I tried to make a brief mention of this under the example section in the readme, but perhaps that could be more clear. Nextjs’ bundle separation is a bit of a magical thing that can be tough to keep in mind at times for sure.
Make sense ! I’m gonna try to rewrite my code to avoid this case too