package compatibility

Compiled from pinned, published npm tarballs · tests/dogfood · measured …

What is measured

Each package is compiled from the exact, pinned, published npm tarball — not a reimplementation or a hand-picked snippet. The same tarball is also the native oracle, so any divergence is a compiler bug, never version skew.

Tests

Own test suite means the package's real tests run against the compiled output. Differential ops means a smaller, harness-authored set of representative calls is compared against native instead — a real signal, but not the same thing. The two are never conflated.

Performance

Charts show Wasm speed relative to the same pinned package in Node on a linear scale; the Node 1× line is the baseline. The global control switches between JS-host and standalone runs. Precompilation adds compile-time-static inputs, which may be optimized away; with it off, inputs arrive after compilation. Static and dynamic results stay separate. Values are medians of 9 warmed-up rounds.

Divergences

Every divergence is a compiler bug, filed as its own issue and linked on the card — never worked around or hidden to make the numbers look better. Packages without a committed, reproducible harness are deliberately not listed.