ES2026 Lands, Temporal Ships, and Decorators Get Demoted: The State of JavaScript Standards
The JavaScript specification process has matured to the point where 'browser support for ES20XX' is the wrong question. Features ship in engines first and enter the standard later, so tracking Stage 4 proposals and individual feature support is the only reliable way to know what you can use. The Decorators downgrade is a concrete warning that even Stage 3 proposals can stall indefinitely without engine vendor commitment.
The 17th edition of ECMA-262, better known as ES2026, was approved on June 30, 2026. Its seven features are all standard library gap-fills: `Map.getOrInsert`, `Iterator.concat`, native Base64/Hex for `Uint8Array`, `Math.sumPrecise`, `Error.isError`, `Array.fromAsync`, and a JSON.parse reviver that can access raw source text to prevent large integer precision loss. No syntax changes made the cut this year.
Beyond the spec, the standards landscape shifted dramatically. Temporal, the long-awaited `Date` replacement, reached Stage 4 in March but missed the ES2026 cutoff and is now slated for ES2027—though Firefox and Chrome already ship it. Decorators, stuck at Stage 3 for four years without a single native browser implementation, were demoted back to Stage 2.7. Records & Tuples were formally withdrawn and replaced by the Composites proposal.
Ecma's membership roster also saw a shakeup. NVIDIA and AMD joined, likely drawn by the new HLSL shader language committee (TC57) rather than JavaScript. ByteDance exited after four years of membership with zero recorded TC39 participation. The total member count hit a record 92.
Feature standardization now trails engine implementation so consistently that the spec is effectively a ratification of what browsers already ship. `Array.fromAsync` was usable in all three major engines by 2023 but only entered the spec in 2026.
The Decorators downgrade exposes a hard truth about the TC39 process: Stage 3 means nothing without at least two engine vendors willing to implement. Four years of stasis and a demotion is a structural failure, not a technical one.
Hardware vendors joining a standards body historically associated with JavaScript is a leading indicator of where Ecma's center of gravity is shifting—toward GPU shading languages, AI agent protocols, and software supply chain standards.
ByteDance's silent exit after four years of zero participation illustrates that membership fees buy a seat but not influence. Alibaba's Error Cause proposal reaching ES2022 and Huawei's Ordinary member voting rights show that actual standards impact requires sustained, in-person committee work.
The addition of Stage 2.7 in 2023 was meant to increase certainty, but the Decorators demotion proves it can also function as a waiting room for proposals that engine vendors are unwilling to commit to.
JavaScript's standard library is catching up to patterns that other languages have had for decades: `Map.getOrInsert` mirrors Python's `setdefault` from 1990, and `RegExp.escape` took ten years to match what Perl and Python shipped in the early 2000s.