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

29 lines
691 B
JSON

{
"name": "@hanzo/replay-shared",
"version": "0.0.1",
"private": true,
"main": "src/index.ts",
"exports": {
".": "./src/index.ts",
"./mobile/*": "./src/mobile/*"
},
"scripts": {
"test": "jest"
},
"dependencies": {
"@hanzo/insights-rrweb": "catalog:",
"@hanzo/insights-rrweb-types": "catalog:",
"fflate": "catalog:",
"fzstd": "catalog:",
"hls.js": "^1.5.7",
"insights-js": "catalog:"
},
"devDependencies": {
"@swc/core": "^1.11.29",
"@swc/jest": "^0.2.37",
"@types/jest": "catalog:",
"jest": "^29.7.0",
"jest-junit": "catalog:"
}
}