Package health checks
The health check reads every package.json in the workspace and runs a set of checks against them entirely offline — no install, no network call. It looks for the kind of drift that's easy to introduce by hand and easy to miss in review: a dependency pinned to two different ranges across the workspace, a literal range where the pnpm catalog already defines one, a sibling package depended on by version instead of workspace:, and a few others.
Running a health check reports package and dependency counts
Tools → Health Check (only offered in a repo with a root package.json) reads every package.json in the workspace and runs a set of offline checks against them — no network call and no need to have run install first. The right panel lists the checks with a pass/warning/skipped badge each; the center pane opens on the overview, with the workspace's package and dependency counts up top.
Captured from the running app by this scenario.
Do this
- Run a health check from the tools menu
This page is generated from apps/e2e/features/package-health.feature, the end-to-end test that drives the feature it describes.