Files
frames/packages/player/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

26 lines
755 B
JSON

{
"package": "@hanzo/frames-player",
"subpaths": {
".": {
"source": "./dist/frames-player.js",
"runtime": {
"script": "./dist/frames-player.global.js",
"import": "./dist/frames-player.js",
"require": "./dist/frames-player.cjs"
},
"types": "./dist/frames-player.d.ts",
"environments": ["browser"]
},
"./slideshow": {
"source": "./dist/slideshow/frames-slideshow.js",
"runtime": {
"script": "./dist/slideshow/frames-slideshow.global.js",
"import": "./dist/slideshow/frames-slideshow.js",
"require": "./dist/slideshow/frames-slideshow.cjs"
},
"types": "./dist/slideshow/frames-slideshow.d.ts",
"environments": ["browser"]
}
}
}