What is this?
The official TC39 repository that tracks every proposal for future JavaScript (ECMAScript) features — a living index of what is being considered for the next versions of the language standard.
The official TC39 repository that tracks every proposal for future JavaScript (ECMAScript) features — a living index of what is being considered for the next versions of the language standard.Is this a tool I install, or just a document I read?Just a document — README tables, with no software to install or run. Each row links to the proposal's own repo and lists its authors, champions, Test262 feature flag and committee meeting notes.
Just a document — README tables, with no software to install or run. Each row links to the proposal's own repo and lists its authors, champions, Test262 feature flag and committee meeting notes.What is Stage 2.7?A newer checkpoint between Stage 2 and Stage 3 for proposals in final refinement. The README currently puts Decorators, Decorator Metadata, ShadowRealm, ESM Phase Imports, Immutable ArrayBuffers and Import Bytes there.
A newer checkpoint between Stage 2 and Stage 3 for proposals in final refinement. The README currently puts Decorators, Decorator Metadata, ShadowRealm, ESM Phase Imports, Immutable ArrayBuffers and Import Bytes there.Why does every proposal link to meeting notes?Because features only advance when the TC39 committee discusses them. The dated notes let you trace a proposal's path through past meetings — Decorators alone has links going back to 2014.
Because features only advance when the TC39 committee discusses them. The dated notes let you trace a proposal's path through past meetings — Decorators alone has links going back to 2014.What about features that never made it?They stay browsable: alongside the active list there are separate 'Finished Proposals' and 'Inactive Proposals' sections, so both shipped history and stalled ideas remain visible.
They stay browsable: alongside the active list there are separate 'Finished Proposals' and 'Inactive Proposals' sections, so both shipped history and stalled ideas remain visible.How is this different from just reading the spec or MDN?The spec and MDN describe JavaScript as it already is; this repo shows what is being proposed next — each entry links the proposal text, its champions, tests and the committee's discussion history.
The spec and MDN describe JavaScript as it already is; this repo shows what is being proposed next — each entry links the proposal text, its champions, tests and the committee's discussion history.What are similar projects?swift-evolution, ecma262, es6features, csharplang, awesome-mcp-servers, awesome-awesomeness, awesome, public-api-lists
swift-evolution, ecma262, es6features, csharplang, awesome-mcp-servers, awesome-awesomeness, awesome, public-api-listsWhich topics is it in?language-design, ecmascript, spec, standards, language, roadmap, directory, specification, catalog, collection, programming-language, reference
language-design, ecmascript, spec, standards, language, roadmap, directory, specification, catalog, collection, programming-language, reference