Skip to content

Snapshots

This server has parsed and cached 13 SHA-pinned snapshots across ECMA-262 and ECMA-402, totaling 35.5 MB on disk. Every clause served carries its (spec, edition, SHA, fetched-at) provenance.

The same data is queryable at runtime via spec.about and spec.snapshots. The hosted Cloudflare Worker additionally accepts at: to address historical SHAs — see Deployment.

Pinned editions

SpecEditionSHAFetched atSize on disk
262es20160b4580532026-05-31T12:10:41.599Z2.1 MB
262es2017101dfd3b2026-05-31T12:10:49.076Z2.3 MB
262es2018fd98c9722026-05-31T12:10:57.420Z2.5 MB
262es2019a8a59dd02026-05-31T12:11:06.637Z2.5 MB
262es2020156c59d92026-05-31T12:11:15.210Z2.7 MB
262es202141ddcc282026-05-31T12:11:23.986Z3.2 MB
262es2022d711ba962026-05-31T12:11:32.862Z3.5 MB
262es2023d048f32e2026-05-31T12:11:42.504Z3.6 MB
262es20240b24a0492026-05-31T12:11:52.254Z3.8 MB
262es202584b38ad82026-05-31T12:12:02.523Z4.0 MB
262main6dcb70f92026-05-31T12:12:13.586Z4.1 MB
402es2025-candidate4a2dae4c2026-05-31T12:12:27.066Z676 KB
402main2c336bf12026-05-31T12:12:27.469Z708 KB

How this stays current

A scheduled CI workflow checks upstream tc39/ecma262 and tc39/ecma402 mains every 4 hours. When anything moved, it bumps the PATCH version of tc39-mcp and republishes. Because package.json is in the docs workflow's paths filter, this page rebuilds along with every refresh — end-to-end latency from upstream merge to updated SHAs above is typically under 10 minutes.

See Deployment / Auto-refresh for the full chain.

Released under the MIT License.