Files
frames/packages/sdk/package-subpaths.json
zooqueen 75094e0d60 frames: publish the toolchain as @hanzo/frames
@hanzo/frame is taken by the hero video primitive — one full-bleed video
element — which has held that name on npm since it shipped. This repo is the
video toolchain: a CLI, a renderer, a studio, a player. Plural is what it is,
so the CLI publishes as @hanzo/frames and the workspace packages follow it
(@hanzo/frames-core, @hanzo/frames-engine, and the rest).

The binary stays `frames`, and now actually ships. The manifest mapped it to
bin/frames.mjs while the file on disk was bin/hyperframes.mjs, so a global
install produced no working command.

The paths that name a package to fetch were pointing elsewhere. The update
check read registry.npmjs.org/frames, a different author's package, and the
npm, bun and pnpm installers would have pulled it over the CLI; the render
image installed the upstream hyperframes; scaffolded projects and the docs
pinned the unscoped name. All of them now name @hanzo/frames.
2026-08-13 18:10:14 -07:00

36 lines
1.1 KiB
JSON

{
"package": "@hanzo/frames-sdk",
"subpaths": {
".": {
"source": "./src/index.ts",
"runtime": "./dist/index.js",
"types": "./dist/index.d.ts",
"environments": ["browser", "bun", "node"]
},
"./adapters/memory": {
"source": "./src/adapters/memory.ts",
"runtime": "./dist/adapters/memory.js",
"types": "./dist/adapters/memory.d.ts",
"environments": ["browser", "bun", "node"]
},
"./adapters/fs": {
"source": "./src/adapters/fs.ts",
"runtime": "./dist/adapters/fs.js",
"types": "./dist/adapters/fs.d.ts",
"environments": ["bun", "node"]
},
"./adapters/headless": {
"source": "./src/adapters/headless.ts",
"runtime": "./dist/adapters/headless.js",
"types": "./dist/adapters/headless.d.ts",
"environments": ["browser", "bun", "node"]
},
"./editing": {
"source": "./src/editing/affordances.ts",
"runtime": "./dist/editing/affordances.js",
"types": "./dist/editing/affordances.d.ts",
"environments": ["browser", "bun", "node"]
}
}
}