False unused alert for webpack-and babel plugins
See original GitHub issueThanks for the great module! (Saved me a lot of time this morning). Adding a few issues to your list of false alerts.
This issue refers to plugin based modules. Specifically in the repo I’m working with, modules that follow the babel-*
or *-loader
naming convention, which are loaded automatically and crucial to the build process even if they are not required/imported.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Customize Webpack and babel configuration with fork of ...
To make this bundle smaller we need to make use of some babel plugin such as 'babel-plugin-transform-imports' which remove unused modules.
Read more >How I solved and debugged my Webpack issue through trial ...
When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.
Read more >React, WebPack and Babel for Internet Explorer 10 and below ...
In your package.json file. change the version of webpack-dev-server to version "2.7.1" (or earlier). "webpack-dev-server": "2.7.1".
Read more >depcheck - UNPKG
572, - False unused alert for webpack-and babel plugins [\#143](https://github.com/depcheck/depcheck/issues/143). 573. 574, **Merged pull requests:**.
Read more >unused-files-webpack-plugin - npm package - Snyk
options.failOnUnused. Emit error instead of warning in webpack compilation result. Default: false; Explicitly set it to true to enable this feature. options.
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 I think the naming is the issue then. Our webpack config files are called
webpack.development.config.js
andwebpack.production.config.js
… I think this pattern is not uncommon for webpack setups. Not sure what the best solution is, maybe to allow us to specify this as a comand-line agument.my webpack config is in “webpack.config.js” file on the root but I still have alerts. using : npm-check --specials bin,webpack