Files
zeekay ad95ed6ca2 State a dependency version once
A version written into a manifest is written into every manifest that wants
the package, and the copies drift. The catalog moves the number out of the
manifest: a manifest names the package, the workspace names the version.

Only names that already resolve to exactly one version move, so nothing
installs differently -- 1424 resolutions are unchanged. Three kinds stay
where they are: a name used at two specifiers, because the catalog would
pick a winner; a name an override already decides, because pnpm records the
overridden specifier; and a name whose one specifier resolved to two
versions, because one entry would unify them.
2026-09-08 23:21:56 -07:00

24 lines
592 B
JSON

{
"name": "@hanzo/products-live-debugger",
"scripts": {
"backend:test": "pytest -c ../../pytest.ini --rootdir ../.. backend/ -v --tb=short"
},
"dependencies": {
"fuse.js": "catalog:"
},
"devDependencies": {
"kea-test-utils": "catalog:"
},
"peerDependencies": {
"@hanzo/icons": "catalog:",
"@hanzo/elements": "catalog:",
"@types/react": "*",
"@types/react-dom": "*",
"clsx": "*",
"kea": "catalog:",
"kea-loaders": "catalog:",
"react": "*",
"react-dom": "*"
}
}