Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
See original GitHub issue🐛 Description
When upgrading from magic-sdk v6.2.1 to magic-sdk v8.1.0 within a perfectly working VueJS3 project, I am getting this warning when serving my app (yarn serve):
WARNING Compiled with 1 warning
warning in ./node_modules/magic-sdk/dist/es/index.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
🌎 Environment
Software | Version(s) |
---|---|
magic-sdk |
8.1.0 |
Browser | Chrome |
yarn |
1.22.17 |
Operating System | Windows |
Issue Analytics
- State:
- Created 2 years ago
- Comments:23 (9 by maintainers)
Top Results From Across the Web
Critical dependency: require function is used in a way in which ...
Critical dependency : require function is used in a way in which dependencies cannot be statically extracted · Subscribe to RSS.
Read more >Critical dependency: require function is used in a way ... - GitHub
The error originates from the esm target, which should not have any require statements. It'd be nice to explore that built module and...
Read more >Incompatible with Webpack - Google Groups
"require function is used in a way, in which dependencies cannot be statically extracted" These errors come when trying to "require" specific modules, ......
Read more >Critical dependency: require function is ... - Auth0 Community
Error message : Critical dependency: require function is used in a way in which dependencies cannot be statically extracted.
Read more >Use es6 import with cesium and angular - CesiumJS
Critical dependency : require function is used in a way in which dependencies cannot be statically extracted. WARNING in .
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
I was about to say I found no issues reported during the build because you already fixed it 🚀.
I’ll update our doc to reflect your suggestion. Thx a lot!
@Ethella I have a fix for react using CRACO
For pure webpack I believe
alias
is nested withresolve
…resolve.alias...
These would be helpful to add to your documentation