4 Commits

Include renames

Author	SHA1	Message	Date
Chris Tate	b6e9e42308	Derive the docs compatibility metadata at build time ... node-v24-compatibility-meta.json held two values derived from the public compatibility artifact: a content hash for the data URL and its row count. Every compatibility change rewrote the hash line, so concurrent changes conflicted on it. next.config.mjs now computes both from the committed artifact and passes them to the page through Next's build-time env, with the same values. The generator no longer writes the file, and its local check compares the public artifact itself.	2026-10-18 21:56:43 -05:00
Chris Tate	5aa450c6b2	docs: migrate to Geistdocs (#611) ... * docs: migrate to Geistdocs * Restore compiler files to main	2026-10-02 00:58:25 -05:00
Chris Tate	8faad2f639	feat: add Node.js compatibility matrix (#284) ... * feat: add Node.js compatibility matrix - Add generated Node.js v24 compatibility inventory with static and dynamic support classifications. - Publish the interactive /compatibility matrix and wire manifest generation into runtime and docs checks. * fix: correct compatibility matrix generation * fix: address PR 284 review findings * fix: address PR 284 review findings * test: exercise stream web loader through npm graph * fix: correct dynamic global availability * fix: keep compatibility module mappings precise	2026-09-02 16:03:36 -05:00
Chris Tate	23d5918a53	init	2026-07-22 18:08:04 -05:00