\n );\n}\n```\n\n## Browser Requirements\n\nWebCodecs H.264 encoding requires Chrome 94+ or Edge 94+. When WebCodecs H.264\nis unavailable, the export automatically falls back to an ffmpeg.wasm worker —\nwhich requires `SharedArrayBuffer` (i.e. Cross-Origin-Isolation headers on the\nhost page). Animated GIF always performs an ffmpeg.wasm palette pass and therefore\nalso requires `SharedArrayBuffer`. The packaged class worker is bundler-safe.\n\nVideo dimensions must be **even**: an odd `width`/`height` is rejected before\ncapture starts rather than rounded (H.264's `yuv420p` cannot encode odd\ndimensions, and GIF export muxes an H.264 intermediate).\n\n### ffmpeg.wasm runtime assets (required)\n\n`@ffmpeg/core` is pinned as a runtime dependency. Hosts **must** publish its ESM\n`ffmpeg-core.js` and `ffmpeg-core.wasm` files from the same origin and pass their\nURLs. Every ffmpeg.wasm path — the encoder fallback, the GIF palette pass, and\ntier-2 audio muxing — throws an actionable error when `coreURL` is absent:\n\n```ts\nconst config = {\n ffmpegWasm: {\n // Copy from node_modules/@ffmpeg/core/dist/esm/ during your build.\n coreURL: '/ffmpeg-core/ffmpeg-core.js',\n wasmURL: '/ffmpeg-core/ffmpeg-core.wasm',\n workerURL: '/vendor/ffmpeg-core.worker.js', // for a multithread core\n },\n};\n```\n\nThis is not merely recommended for offline/CSP deployments — it is required.\n`@ffmpeg/ffmpeg`'s `load()` otherwise falls back to a hard-coded\n`https://unpkg.com/@ffmpeg/core@/…` URL, silently fetching and executing\nunpinned third-party code mid-export. Squisq refuses to trigger that fallback; a\nGIF export with no `ffmpegWasm` now fails immediately instead of after capturing\nevery frame. `packages/site/vite.config.ts` + `packages/site/src/ffmpegWasmConfig.ts`\nare a complete worked example for Vite (including the GPL notice that must travel\nwith the core files). To deliberately use a remote core, name that URL as\n`coreURL` explicitly.\n\nUse `supportsWebCodecs()` to probe at runtime:\n\n```ts\nimport {\n supportsWebCodecs,\n supportsWebCodecsH264,\n supportsWebCodecsAac,\n} from '@bendyline/squisq-video-react';\n\nif (!supportsWebCodecs()) {\n // ffmpeg.wasm fallback will be used (needs Cross-Origin-Isolation)\n}\n```\n\n**Audio tiers.** MP4 audio is muxed via WebCodecs AAC when available\n(`supportsWebCodecsAac()`), then via ffmpeg.wasm when cross-origin isolation is\navailable, and otherwise skipped with `audioIncluded: false` plus an\n`audioSkippedReason`. Audio problems never fail the export — the video always\ncompletes. GIF skips audio preparation entirely. `supportsWebCodecsH264(config)` probes a specific encoder\nconfiguration; `EncoderConfig` and `FfmpegWasmLoadConfig` are also exported.\n\n## Full API Reference\n\nSee [docs/API.md](https://github.com/bendyline/squisq/blob/main/docs/API.md)\nfor complete prop tables, `VideoExportConfig`, and the encoder utilities.\n\n## Related Packages\n\n| Package | Description |\n| -------------------------------------------------------------------------------- | ------------------------------------------------- |\n| [@bendyline/squisq-video](https://www.npmjs.com/package/@bendyline/squisq-video) | Headless video/GIF rendering and WASM helpers |\n| [@bendyline/squisq](https://www.npmjs.com/package/@bendyline/squisq) | Headless core — schemas, templates, markdown |\n| [@bendyline/squisq-react](https://www.npmjs.com/package/@bendyline/squisq-react) | React components for rendering docs |\n| [@bendyline/squisq-cli](https://www.npmjs.com/package/@bendyline/squisq-cli) | CLI for document conversion and MP4/GIF rendering |\n\n## License\n\nSquisq-authored code in this package is\n[MIT licensed](https://github.com/bendyline/squisq/blob/main/LICENSE).\n\nThe separately distributed `@ffmpeg/core` WebAssembly runtime has an upstream\ndependency on FFmpeg and external libraries. The 0.12.9 package declares\nGPL-2.0-or-later and is distributed under those terms. This package ships\n[`NOTICE.md`](./NOTICE.md) and the complete\n[`COPYING.GPL-2.0.txt`](./COPYING.GPL-2.0.txt). Hosts that publish\n`ffmpeg-core.js` or `ffmpeg-core.wasm` must publish those materials with the\nruntime and preserve equivalent access to the exact corresponding source\nidentified in the notice.\n","readmeFilename":"README.md"}