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.

Modules with same name as a built-in (e.g. 'path') are incorrectly identified as unused dependency

See original GitHub issue

It appears as though path is incorrectly identified as an unused dependency.

dmurray@ss9:...andbox/depcheck-path 0> npm run depcheckjson

> depcheck-path@1.0.0 depcheckjson /home/dmurray/sandbox/depcheck-path
> depcheck --json|json

{
  "dependencies": [
    "path"
  ],
  "devDependencies": [],
  "missing": {},
  "using": {
    "depcheck": [
      "/home/dmurray/sandbox/depcheck-path/package.json"
    ]
  },
  "invalidFiles": {},
  "invalidDirs": {}
}
dmurray@ss9:...andbox/depcheck-path 0>

This is a trivial demo project, containing server.js which includes log.js, which uses path.

To reproduce:

unpack depcheck-path.zip
npm install
npm run depcheckjson

depcheck-path.zip

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:10 (3 by maintainers)

Top GitHub Comments

1reaction

Berkmann18commented, Oct 23, 2018

@rumpl In my case, I’m here because of this issue where the dependency (lodash) was classified as unused… Which wasn’t.

Regarding using native modules (read dependencies that are already imported), I guess it would make sense to flag said dependencies as unneeded (note: the “unneeded” as opposed to the “unused”).

0reactions

stale[bot]commented, Mar 1, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.