Files
ui/pkgs/data/package.json
zeekay f9625f7982 fix(data): stop pkgs/data from being publishable over the real package
Two packages in this repo claim the name @hanzo/data. pkg/data is 1.2.1,
matches npm, and is what pkg/ui depends on. pkgs/data is a 0.1.0 stub with
half the source — and it sits under pkgs/*, which publish.yml auto-publishes
on any version change. A bump there would ship the stub and npm would tag it
latest, silently downgrading every consumer.

publish.yml already skips private packages, so marking it private removes the
hazard without deleting anyone's in-flight work. This is the same shape as the
@hanzo/event incident: two homes for one name, the wrong one wired to ship.
2026-07-25 15:22:18 -07:00

42 lines
1.2 KiB
JSON

{
"name": "@hanzo/data",
"version": "0.1.0",
"private": true,
"type": "module",
"description": "Hanzo Data \u2014 cross-platform, metadata-driven data-app components (typed fields, record table, record card) on @hanzo/gui. The universal object/field/record/view layer that powers any Base-backed CRM, CMS, or commerce app on web, native (iOS), and desktop.",
"exports": {
".": {
"types": "./src/index.ts",
"default": "./src/index.ts"
}
},
"main": "./src/index.ts",
"module": "./src/index.ts",
"types": "./src/index.ts",
"sideEffects": false,
"files": [
"src"
],
"scripts": {
"tc": "tsc --noEmit",
"typecheck": "tsc --noEmit",
"build": "tsc --outDir dist --declaration --emitDeclarationOnly false --module ESNext --moduleResolution bundler --jsx react-jsx --esModuleInterop true --skipLibCheck true --sourceMap true"
},
"peerDependencies": {
"@hanzo/gui": ">=7.2.2",
"react": ">=19"
},
"devDependencies": {
"@hanzo/gui": "7.2.2",
"@hanzogui/config": "7.3.0",
"@types/react": "^19.1.10",
"react": "^19.0.0",
"typescript": "^5.7.2"
},
"publishConfig": {
"access": "public"
},
"license": "BSD-3-Clause",
"author": "Hanzo AI <[email protected]>"
}