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

30 lines
769 B
JSON

{
"name": "@hanzo/auth-proxy",
"version": "1.0.0",
"description": "Cross-region OAuth proxy for Insights Cloud (oauth.hanzo.ai)",
"keywords": [
"auth",
"multi-region",
"oauth",
"insights",
"proxy"
],
"license": "MIT",
"author": "Insights Inc.",
"scripts": {
"dev": "wrangler dev",
"deploy": "wrangler deploy",
"cf-typegen": "wrangler types",
"test": "vitest",
"test:watch": "vitest watch",
"typecheck": "tsgo --noEmit"
},
"devDependencies": {
"@cloudflare/workers-types": "^4.20260120.0",
"typescript": "catalog:",
"vite-tsconfig-paths": "catalog:",
"vitest": "^4.1.0",
"wrangler": "catalog:"
}
}