Files
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

40 lines
886 B
TypeScript

import { defineConfig } from "tsup";
export default defineConfig({
tsconfig: "tsconfig.lib.json",
entry: {
index: "src/index.ts",
"styles/tailwind-preset": "src/styles/tailwind-preset.ts",
},
format: ["esm"],
dts: true,
sourcemap: true,
clean: false,
splitting: true,
external: [
"@codemirror/autocomplete",
"@codemirror/commands",
"@codemirror/lang-css",
"@codemirror/lang-html",
"@codemirror/lang-javascript",
"@codemirror/lang-markdown",
"@codemirror/language",
"@codemirror/search",
"@codemirror/state",
"@codemirror/theme-one-dark",
"@codemirror/view",
"@hanzo/frames-core",
"@hanzo/frames-player",
"@hanzo/frames-sdk",
"@phosphor-icons/react",
"bpm-detective",
"dompurify",
"marked",
"mediabunny",
"react",
"react-dom",
"react/jsx-runtime",
"zustand",
],
});