mirror of
https://github.com/hanzoai/ui.git
synced 2026-11-20 20:07:34 +00:00
The package was never published under EITHER name — `npm view @hanzo/gitops` and `@hanzo/cd` both returned E404 — so `pkg/ui/src/gitops.ts` (`export * from '@hanzo/gitops'`) and the `>=0.1.0` peer dep pointed at nothing and broke every clean install of @hanzo/ui. Publishing exposed a second break one level down: @hanzo/gitops peers on @hanzo/canvas >=0.2.0, and the registry still had canvas at 0.1.0 while the monorepo was on 0.2.1. Publishing the first package alone only moved the ETARGET deeper. Both are now on the registry, and a clean `npm install @hanzo/[email protected]` resolves — 673 packages, no errors. pkgs/gitops -> pkgs/cd and @hanzo/gitops -> @hanzo/cd: the surface is the CD surface (cd.hanzo.ai, apps/cd), and the old name only ever described the mechanism. Every reference in the monorepo moved with it; the old name is deprecated on npm pointing here rather than left as a second way to install the same code. Co-authored-by: Hanzo Dev <[email protected]>
27 lines
744 B
JSON
27 lines
744 B
JSON
{
|
|
"name": "cd",
|
|
"private": true,
|
|
"version": "0.1.0",
|
|
"type": "module",
|
|
"description": "Hanzo CD — the dedicated deploy dashboard served at cd.hanzo.ai (a @hanzo/cd + @hanzo/canvas SPA over /v1/deploy). Replaces the ArgoCD UI fork.",
|
|
"scripts": {
|
|
"dev": "vite",
|
|
"build": "tsc -b && vite build",
|
|
"typecheck": "tsc --noEmit -p tsconfig.app.json",
|
|
"preview": "vite preview --port 4173"
|
|
},
|
|
"dependencies": {
|
|
"@hanzo/canvas": "workspace:*",
|
|
"@hanzo/cd": "workspace:*",
|
|
"react": "^19.2.4",
|
|
"react-dom": "^19.2.4"
|
|
},
|
|
"devDependencies": {
|
|
"@types/react": "^19.2.14",
|
|
"@types/react-dom": "^19.2.3",
|
|
"@vitejs/plugin-react": "^6.0.3",
|
|
"typescript": "~6.0.2",
|
|
"vite": "^8.1.4"
|
|
}
|
|
}
|