npm workspace lockfile inspector

What it does

Explain how workspace dependency declarations map to supplied package-lock entries and identify missing or mismatched resolutions.

How to use it

1. Import a local workspace bundle with package.json files and a version 2 or 3 package-lock.json, then inspect its declarations.
2. Review source-linked resolution paths, hoisted or nested entries and reported disagreements. Export a local diagnostic report.
3. No packages are installed, files rewritten or registries contacted. This is a consistency explanation, not an npm dependency solver.

Example

A workspace declaring a dependency range resolves to a hoisted node_modules entry; a second declaration is flagged when its recorded version does not satisfy the range.

Methodology

Root and matching supplied workspace manifests are compared with the npm lockfile v2/v3 packages map. Each declaration records its own lock-metadata agreement separately from version-range satisfaction, following closest nested and ancestor entries or bounded local workspace links. Locations and searched paths remain visible.

Limitations

2,000 folder files; 5 MB ZIP / 100 entries / 10 MB expanded; 256 KB per manifest, 6 MB per lockfile / 10 MB combined text, in decimal bytes. Up to 100 manifests, 100 workspace patterns, 20,000 lock entries, 5,000 declarations, 16 link hops, 2 million report characters and 30 seconds. Missing manifests, unsupported protocols and root overrides remain explicit gaps. Optional absence does not prove install applicability. No registry lookup, node_modules inspection, install, lock rewriting or peer/override solver.

Automation

This tool runs in your browser. No upload API or MCP endpoint is available.