Better monorepo support

Many projects these days are using a monorepo structure where the repo has a main package.json file which manage multiple package directories that have their own package.json files.

Generally the main package.json is fairly light on for dependencies, with the sub packages having the bulk.

For example, my workplace shows https://backyourstack.com/ioof-holdings/dependencies, which is a far shot off the full list of dependencies.

It would be great if perhaps you could scan deeper into the folder structure and extract all the package.json files for analysis.

[alessiostalla]

Perhaps an optional top-level file could be used to direct your search so you don’t have to recurse. E.g. .backyourstack.yml:

dependencySources:
 - backend/pom.xml
 - frontend/package.json

[eins78]

Similar problem: having several project in 1 repository. Example: A clojure backend with a JS client, each in their own subdirectories https://github.com/leihs/leihs-procure

It doesn’t use any tools like lerna, and the Github API does not expose dependencies (although in some cases they must have the data internally, because they show the “Dependency Graph”), so I don’t see any obvious solution apart from recursing into subfolders (up to a a certain level).