mirror of
https://github.com/hanzoai/frames.git
synced 2026-09-24 00:08:03 +00:00
zooqueen
75094e0d60
@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.
22 lines
656 B
TypeScript
22 lines
656 B
TypeScript
import { defineConfig } from "tsup";
|
|
import { readFileSync } from "node:fs";
|
|
|
|
const packageVersion = JSON.parse(readFileSync(new URL("./package.json", import.meta.url), "utf8"))
|
|
.version as string;
|
|
|
|
export default defineConfig({
|
|
entry: ["src/frames-player.ts", "src/slideshow/frames-slideshow.ts"],
|
|
format: ["esm", "cjs", "iife"],
|
|
globalName: "HyperframesPlayer",
|
|
noExternal: ["@hanzo/frames-core"],
|
|
dts: true,
|
|
clean: true,
|
|
minify: true,
|
|
sourcemap: true,
|
|
define: {
|
|
__FRAMES_RUNTIME_CDN_URL__: JSON.stringify(
|
|
`https://cdn.jsdelivr.net/npm/@hanzo/frames-core@${packageVersion}/dist/hyperframe.runtime.iife.js`,
|
|
),
|
|
},
|
|
});
|