mirror of
https://github.com/hanzoai/frames.git
synced 2026-09-24 00:08:03 +00:00
@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.
26 lines
886 B
JavaScript
26 lines
886 B
JavaScript
#!/usr/bin/env node
|
|
|
|
import { readFileSync } from "node:fs";
|
|
import { join } from "node:path";
|
|
|
|
const root = join(import.meta.dirname, "..");
|
|
const { version } = JSON.parse(readFileSync(join(root, "package.json"), "utf8"));
|
|
const expected = `@hanzo/frames-core@${version}/dist/hyperframe.runtime.iife.js`;
|
|
const bundles = [
|
|
"dist/frames-player.js",
|
|
"dist/frames-player.cjs",
|
|
"dist/frames-player.global.js",
|
|
];
|
|
|
|
for (const bundle of bundles) {
|
|
const source = readFileSync(join(root, bundle), "utf8");
|
|
if (!source.includes(expected)) {
|
|
throw new Error(`${bundle} does not pin the injected runtime to ${version}`);
|
|
}
|
|
if (source.includes("@hanzo/frames-core/dist/hyperframe.runtime.iife.js")) {
|
|
throw new Error(`${bundle} still contains an unversioned runtime URL`);
|
|
}
|
|
}
|
|
|
|
console.log(`Verified Player runtime injection is pinned to @hanzo/frames-core@${version}.`);
|