Bug with subdirectories?

[smazurov]

I'm running into an issue where files in subdirectories aren't correctly checked (at least for peerDependancies) for require statements

Quick test:

./package.json and npm install

{
  "name": "test-dep",
  "version": "1.0.0",
  "description": "test peerdeps",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "css-modules-require-hook": "^2.1.0",
    "postcss-modules-extract-imports": "^1.0.0",
    "postcss-modules-local-by-default": "^1.0.0",
    "postcss-modules-scope": "^1.0.0",
    "postcss-modules-values": "^1.1.1"
  }
}

./entry.js

require('css-modules-require-hook');

Running depcheck:

No unused dependencies

Working as intended

Breaks:

make a folder test/ and move entry.js there:

$ mkdir test && mv entry.js test

Running depcheck:

Unused devDependencies

• postcss-modules-extract-imports
• postcss-modules-local-by-default
• postcss-modules-scope
• postcss-modules-values

---

Debug info:

$ npm --version
3.3.12
$ node --version
v5.1.0

depcheck is latest installed with npm install -g depcheck

---

Is this desired behavior? Quick look at the folder scanning, it seems to be going into (sub)directories unless they're ignored.

[lijunle]

Confirmed as a bug, It is caused by subdir is passed to checkDirectory by mistake (code), should be (root) dir.

[lijunle]

Release 0.5.11 to fix this.

[smazurov]

Thanks a ton, this is an awesome tool (I use it with npm-check), thank you for maintaining it.