Publish blit binary via npm (blit-bin)

[pcarrier]

What

Publish the blit binary to npm so it can be installed (npm i -g blit-bin) and bundled into downstream tools.

This adds a thin blit-bin launcher plus per-platform blit-bin-<os>-<cpu>[-musl] data packages. The launcher lists the platform packages as optionalDependencies with os/cpu/libc filters, so npm installs exactly one prebuilt binary — the one matching the host — and nothing else.

graph TD
  U["npm i blit-bin"] --> L["blit-bin launcher"]
  L -->|"optionalDependencies: os, cpu, libc"| P{"host"}
  P -->|"linux x64 glibc"| A["blit-bin-linux-x64"]
  P -->|"linux x64 musl"| B["blit-bin-linux-x64-musl"]
  P -->|"linux arm64"| C["blit-bin-linux-arm64 (plus -musl)"]
  P -->|"darwin arm64"| D["blit-bin-darwin-arm64"]
  P -->|"win32 x64"| E["blit-bin-win32-x64"]
  L -.->|"bin launcher execs"| A

Loading

Import API

The default export is the absolute filesystem path to the blit executable (the ffmpeg-static / @esbuild/* convention), so downstreams can spawn it:

import blit from "blit-bin";
import { spawn } from "node:child_process";
spawn(blit, ["open"], { stdio: "inherit" });

Identical in CommonJS (const blit = require("blit-bin")). Resolution happens eagerly at import and throws an actionable error if the matching optional package was omitted. Lower-level helpers (binaryPath, binaryName, candidatePackages, isMusl) are available as named exports and on the blit-bin/resolve subpath. Ships dual ESM (index.mjs) + CJS (index.js) with an exports map and index.d.ts typing the default as string.

Pipeline

• bin/build-npm-bin-packages repackages the existing release artifacts (blit_<ver>_<os>[-musl]_<arch>.tar.gz + blit_<ver>_windows_x86_64.zip) into the per-platform packages and the launcher, pinning optionalDependencies to the release version.
• bin/publish-npm-bin-packages publishes platform packages first, launcher last.
• New publish-bin-npm job in release.yml (needs release) downloads tarballs-* + windows-x86_64 and publishes with --provenance --access public (OIDC — same tokenless setup as the existing @blit-sh/* job).

The platform matrix tracks exactly what CI builds today (linux x64/arm64 glibc+musl, darwin arm64, win32 x64); the generator auto-discovers any artifact, so adding e.g. darwin-x64 later needs no script change.

Verified locally

• Generator emits all packages + launcher once each with correct os/cpu/libc and version pinning.
• ESM import blit from and CJS require both return the path and spawn the binary; CLI (bin/blit) works with exit-code/signal passthrough.
• npm pack --dry-run file lists clean; tsc (nodenext) confirms default is string and the /resolve subpath resolves; release.yml parses and artifact names match the build workflows.

[github-actions]

Coverage

Crate	Lines	Functions	Regions
alacritty-driver	63.7% (626/982)	67.1% (49/73)	64.3% (919/1429)
browser	0.0% (0/807)	0.0% (0/65)	0.0% (0/1370)
cli	28.1% (1208/4299)	41.3% (171/414)	31.1% (2182/7019)
compositor	1.0% (93/9234)	2.0% (8/400)	1.2% (146/12408)
fonts	76.8% (486/633)	85.5% (47/55)	77.9% (922/1183)
gateway	25.7% (362/1411)	29.0% (36/124)	19.4% (449/2318)
proxy	18.3% (150/818)	20.9% (24/115)	20.4% (260/1277)
remote	71.5% (1975/2763)	81.4% (188/231)	74.1% (3737/5045)
sd-notify	73.9% (68/92)	100.0% (6/6)	83.2% (109/131)
server	18.7% (2186/11701)	33.6% (251/748)	20.1% (3660/18180)
ssh	1.9% (7/374)	3.2% (1/31)	0.7% (4/613)
webrtc-forwarder	2.7% (72/2624)	2.1% (4/187)	1.2% (50/4335)
webserver	63.5% (753/1185)	70.8% (121/171)	67.8% (1380/2034)
Total	21.6% (7986/36923)	34.6% (906/2620)	24.1% (13818/57342)