Can't resolve 'process/browser'
See original GitHub issueHi
Firstly, Thank for your work.
I use webpack 5.1 and canvg 3.0.9 Today when complie I get this error log
ERROR in ./node_modules/canvg/lib/index.es.js 1933:16-23
Module not found: Error: Can't resolve 'process/browser' in '*****\node_modules\canvg\lib'
Did you mean 'browser.js'?
BREAKING CHANGE: The request 'process/browser' failed to resolve only because it was resolved as fully specified
(probably because the origin is a '*.mjs' file or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
Have any idea thank!
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
Error: Can't resolve 'process/browser' #365 - GitHub
When using 3.1.19 I'm getting the following error: ERROR Failed to compile with 1 errors 11:17:18 error in .
Read more >Webpack 5 - Uncaught ReferenceError: process is not defined
In webpack 5 automatic node.js polyfills are removed. In the migration docs it is mention that. Try to use frontend-compatible modules ...
Read more >ES modules via NPM build error "Can't resolve 'pro...
When we remove line 5: "process: "process/browser", we can build but then we have other CORB issues. Everything is working fine when we...
Read more >r/npm - "Can't resolve 'process/browser.js'" error when running ...
"Can't resolve 'process/browser.js'" error when running npm run prod. r/npm - "Can't resolve 'process/browser.js'.
Read more >react webpack < 5 used to include polyfills for node.js core ...
react-scripts 5 webpack Module not found: Error: Can't resolve 'fs' ... { "process": require.resolve("process/browser") }' - install 'process' If you don't ...
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 FreeTop 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
Top GitHub Comments
For those in the same boat, I was able to solved it by adding a new rule to webpack (version 5):
save my day, thanks very much!