Dependencies between the stack's projects
Each project with its consumers. The stack repos that declare a dependency on it. A breaking change has to be carried through each of them, and through any consumer that no manifest declares. Only the stack's own projects are listed, so a consumer outside the stack is not here.
Only each repo's root manifests are read. A manifest shows what a repo declares, which is not always what its code imports, and a dependency that no manifest states, such as a sibling checkout a test reads, is not here. The kind is the manifest table a dependency is declared in, not how much it matters: an app that bundles what it builds declares everything as dev.
Read from the repos' manifests on .
- runtime Under dependencies in package.json, or a normal dependency of a crate.
- peer Under peerDependencies, and required.
- optional peer Under peerDependencies, and marked optional.
- optional Under optionalDependencies.
- build A crate's build dependency.
- dev Under devDependencies, a dev dependency of a crate, or anything a test or tooling crate uses.