False positives for nyc, babel, eslint, webpack and its loaders
See original GitHub issueI’ve read through all the issues but this cannot get this tool to stop giving out false positives.
For example, I’ve
.babelrc
{
"presets": ["save"],
...
}
yet I get babel-preset-save
as unused. Same goes for several webpack, eslint loaders.
It also lists out things like nyc, cross-env as unused but they are being used in npm scripts.
I tried depcheck --specials=webpack,eslint,babel
but no luck. I still get ton of false positives.
What am I missing?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:12
- Comments:8 (2 by maintainers)
Top Results From Across the Web
webpack-babel-multi-target-plugin-fix - npm package - Snyk
A Webpack plugin that works with Babel to allow differential loading - production deployment of ES2015 builds targeted to modern browsers, ...
Read more >eslint giving false positive - typescript - Stack Overflow
I'm new to Webpack and have ran into an issue with eslint and Typescript. eslint is telling me that I'm missing return type...
Read more >eslint-plugin-import | Yarn - Package Manager
This plugin intends to support linting of ES2015+ (ES6+) import/export syntax, and prevent issues with misspelling of file paths and import names. All...
Read more >babel-loader - webpack
Make sure you are transforming as few files as possible. Because you are probably matching /\.m?js$/ , you might be transforming the node_modules...
Read more >Code coverage · mochapack - GitHub Pages
Only the files that are listed in this list, are covered. instrument: false stops nyc from instrumenting your code, that's the task of...
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 here
I got the same for all webpack loaders and babel-polyfill, which I am using as an entry point in the webpack config. Essentially, anything that isn’t explicitly imported anywhere.
One caveat: I also briefly got eslint as a false positive, but after another
npm i
that didn’t happen anymore.