How the ffmpeg.wasm cores served from /v2/ffmpeg-core/ are built
(@ffmpeg/core-mt@0.13.0-finalcut.3, @ffmpeg/core@0.13.0-finalcut.3, @ffmpeg/core-legacy@0.12.10)

Build recipe: https://github.com/yishengjiang99/ffmpeg.wasm at commit bf6a3f376c11f1e0482deb9a9187e1e6d2b04e0a
  archive here: ffmpeg.wasm-fork-bf6a3f37.tar.gz (Dockerfile, build/*.sh incl. source patches, src/bind, src/fftools-*)
Toolchain image: emscripten/emsdk:4.0.23@sha256:86537645c51e44899812d29820ee3b64b96c321ebb2aba4416a04ceeb1bcde62

At the commit above: scripts/ci-local.sh (Docker build of mt and st; sources pinned in build/sources.lock.json; source patches live in build/ffmpeg.sh, build/x264.sh and src/fftools-*). The fallback core 0.12.10 is built from legacyBuildRecipe. Cores of 0.13.0-finalcut.3 were built by the fork workflow core-build, run 38321096611.

Fallback core @ffmpeg/core 0.12.10: https://github.com/ffmpegwasm/ffmpeg.wasm at commit 71aa99d37c02a7b4c435275ca9ef50e612f6efa1
  archive here: ffmpeg.wasm-71aa99d3.tar.gz; toolchain image emscripten/emsdk:3.1.40
  At the commit above: `make prd` (single-thread, @ffmpeg/core) and `make prd-mt` (multithreaded, @ffmpeg/core-mt), which run `docker buildx build` on the Dockerfile with FFMPEG_ST=yes / FFMPEG_MT=yes. The Dockerfile fetches each library at the ref listed below.

Every library source the Dockerfile fetches is in this directory at the exact commit/tag it uses
(see versions.json and SHA256SUMS). To build offline, point each `ADD <git url>#<ref>` line in the
Dockerfile at the matching extracted archive here.

We serve the npm packages unmodified (sha256 of each served file: /v2/ffmpeg-core/manifest.json).