Webpack warning "dependencies cannot be statically extracted"
See original GitHub issueWebpack 3.12.0 shows a warning:
warning in ./node_modules/@lottiefiles/lottie-player/dist/lottie-player.js
1:263-264 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:19 (3 by maintainers)
Top Results From Across the Web
require function is used in a way in which dependencies ...
25:24-31 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted.
Read more >Webpack UMD: Critical dependency... cannot be statically ...
If I change the module to commonjs it works perfectly fine without warnings or errors. typescript · webpack · umd · Share.
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 >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 >Node.js – WARNING in Critical dependency: require function ...
js – WARNING in Critical dependency: require function is used in a way in which dependencies cannot be statically extracted. angularnode.jswebpack. After ...
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

Same issue here.
Just installed the latest package, warning still occurring