- 🐣 for checking against contents of package.json use the package.json closest to the file being cruised, instead of the one in the directory the cruise was started from. This behaviour is more consistent with how node & npm work, yielding more accurate results and less false positives (issue #35 / PR #38 , both contributed by @ajafff - sehr vielen Dank für diesen Beitrag, Herr Meinhardt!)
This is a breaking change a.c.t. dependency-cruiser@2.x.x
Breaking change: look up closest package.json
impact classification: low
You might see different output from dependency-cruiser in the following cases.
- You have
package.json's in the directory-tree below the directory you're running dependency-cruiser from. This is typical in mono-repos.
For mono-repos this amounts todependency-cruiser will use the - You do not have a
package.jsonin the directory you're running dependency-cruiser from.
dependency-cruiserwill use the first package.json it finds going up in the directory tree.
The different output is more accurate in all cases, so you probably want to use v3.x.x even if your code base fits in one of the above criteria. If not (or if not right now) you can still use v2.x.x for a while.