mirror of
https://github.com/hanzoai/frames.git
synced 2026-08-07 18:08:30 +00:00
zooqueenandhanzo-dev
12aa96ed7e
Forked from HyperFrames (Apache-2.0), full history preserved. Hosts are mapped explicitly and BEFORE the identifier rename, because hyperframes.heygen.com is not decoration: 175 of its occurrences are $schema identifiers that a validator dereferences. A blind rename would have left them naming a host that never serves them. The schema files are in this repo under docs/schema, so the mapped host is one we can actually serve -- that is the condition that makes the rewrite safe, and serving them is a deploy task, not an edit. docs/schema/hyperframes.json is renamed to frames.json to match the identifier it is now published under. api.heygen.com and the CLI auth against heygen.com are left UNRENAMED on purpose. They are a dependency on HeyGen's SaaS, not a name of ours to take, and the right move is to remove that integration rather than rebrand it. LICENSE and CREDITS.md are untouched; NOTICE records the lineage. Co-authored-by: Hanzo Dev <dev@hanzo.ai>
31 lines
1.5 KiB
TypeScript
31 lines
1.5 KiB
TypeScript
/**
|
|
* CJS-interop banner prepended to the ESM handler bundle.
|
|
*
|
|
* Lambda's Node 22 runtime treats `.mjs` as ESM, which has no `require`,
|
|
* `__filename`, or `__dirname`. The handler bundle inlines CJS deps that
|
|
* assume all three exist at module scope:
|
|
* - postcss et al. call top-level `require(...)`
|
|
* - wawoff2's emscripten build (pulled in unconditionally via
|
|
* producer → fontCompression) reads `__dirname` at module scope
|
|
* Without the shims the handler throws "Dynamic require of <X> is not
|
|
* supported" / "__dirname is not defined in ES module scope" at import time,
|
|
* before it can run — which is exactly how a freshly deployed stack crashed
|
|
* on every render (#1932).
|
|
*
|
|
* This mirrors the producer's own CJS banner (packages/producer/build.mjs);
|
|
* the handler bundle inlines producer source, so it needs the same shim.
|
|
*
|
|
* Kept in its own module (not inline in build-zip.ts, which self-executes on
|
|
* import) so build-zip.test.ts can import the exact banner, bundle a fixture
|
|
* with it, and assert the globals actually resolve.
|
|
*/
|
|
export const HANDLER_BANNER = [
|
|
"// frames-aws-lambda handler bundle",
|
|
'import { createRequire as __hf_createRequire } from "module";',
|
|
'import { fileURLToPath as __hf_fileURLToPath } from "url";',
|
|
'import { dirname as __hf_dirname } from "path";',
|
|
"const require = __hf_createRequire(import.meta.url);",
|
|
"const __filename = __hf_fileURLToPath(import.meta.url);",
|
|
"const __dirname = __hf_dirname(__filename);",
|
|
].join("\n");
|