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

31 lines
903 B
JSON

{
"name": "@hanzo/elements",
"version": "0.0.0",
"homepage": "https://storybook.dev.insights.dev/",
"license": "MIT",
"source": "src/index.ts",
"main": "dist/index.js",
"types": "dist/index.d.ts",
"scripts": {
"build": "pnpm build:source && pnpm build:types && ls -lah dist/",
"build:source": "echo \"Building source\" && node build.mjs",
"build:types": "echo \"Building types\" && tsup src/index.ts --dts-only",
"prepublishOnly": "pnpm build",
"typecheck": "tsc --noEmit",
"typecheck:tsgo": "tsgo --noEmit"
},
"dependencies": {
"kea": "^4.0.0-pre.3",
"kea-router": "^3.4.1"
},
"devDependencies": {
"@hanzo/esbuilder": "workspace:*",
"tsup": "catalog:",
"typescript": "catalog:"
},
"peerDependencies": {
"react": "*",
"react-dom": "*"
}
}