warning with webpack5
See original GitHub issueDescribe the bug
not ok when using webpack5.
Expected behavior
should use default export instead of named export
Actual behavior
there comes a warning as blow: in /node_modules/esri-leaflet/src/EsriLeaflet.js Should not import the named export ‘version’ (reexported as ‘VERSION’) from default-exporting module (only default export is available soon)
To Reproduce
using webpack5
Environment Information
- Version of Leaflet (
L.version
): 1.7.1 - Version of Esri Leaflet (
L.esri.VERSION
): 2.5.2 - Your OS: window 10
- Browser and Version Chrome 87.0.4280.88
Additional context
webpack: 5.11.0;
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
component-driven/cypress-axe - Warnings with Webpack 5
WARNING in ./node_modules/cypress-axe/dist/index.js 16:47-54 Critical dependency: require function is used in a way in which dependencies ...
Read more >webpack compiles with warnings, but the warning messages ...
I am using the latest versions of Node, NPM, webpack and the UglifyJS webpack plugin. I am running this on Windows. I get...
Read more >warnings-to-errors-webpack-plugin - npm
warnings -to-errors-webpack-plugin. TypeScript icon, indicating that this package has built-in type declarations.
Read more >webpack.Compilation.warnings JavaScript and Node.js code ...
When process.env.CI = true, warnings are treated as failures. Most CI servers set this automatically.', stats.compilation.warnings);
Read more >Stats - webpack
warning. This option does not have any effect when using the Node.js API. ... 'summary', none, Output webpack version, warnings count and errors...
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
here is the demo repo to reproduce : https://github.com/wwwwlm-work/issue-demo
blow is what I did to prevent that warning temporarily:
Hello
There is any solution on this?
when compiling webpack 5 get this erros, and this package is a dependency of other packages, forking it’s not a solution.´
Thanks Daniel