Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

False positive when using inline Webpack loader

See original GitHub issue

This tool returns a false positive when calling a script using an inline Webpack loader. For instance:

require('script-loader!slick-carousel');

Here, depcheck considers slick-carousel as unused.

Issue Analytics

State:
Created 6 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

rumplcommented, Jan 31, 2020

@jpetitcolas A year and a week later, this is fixed, will be available in the next release, next week surely

0reactions

rumplcommented, Jan 31, 2020

@znarf what’s an Open Collective bounty?

Top Results From Across the Web

False positives for nyc, babel, eslint, webpack and its loaders

Yep, noticing that all my webpack loaders are showing up as unused dependencies, even while using the specials=webpack flag.

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...

Loader Interface - webpack

Loaders may be added inline in requests and disabled via inline prefixes, ... Call this method passing false to make the loader's result...

Asset Modules - webpack

Previously achievable by using file-loader . asset/inline exports a data URI of the ... When using the old assets loaders (i.e. file-loader /...

Optimization - webpack

Tells webpack which algorithm to use when choosing chunk ids. Setting optimization.chunkIds to false tells webpack that none of built-in algorithms should be...