Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
JavaScript’s future is an incremental evolution of ECMAScript: some changes are already part of the published standard, while others remain proposals that may change or take time to reach the runtimes you use. The latest completed release in the cited specification summary is ECMAScript 2025; the 2026 specification is identified as the seventeenth edition, and TC39 continues to consider additional proposals.
What’s next for JavaScript?
JavaScript is the language commonly associated with the standardized specification called ECMAScript. Ecma International’s Technical Committee 39 (TC39) develops that standard. To understand what is actually available, separate three things: features already included in a published edition, proposals still moving through TC39, and support in a particular browser or server runtime.
A proposal is not a feature that developers can safely assume exists. Its stage signals how far the committee’s process has advanced; it does not guarantee a release date or availability in a specific browser or version of Node.js. Check compatibility for the exact target environments before relying on a feature.
What new JavaScript features are already standardized?
ECMAScript 2025, the sixteenth edition, includes several notable additions. These are standardized features, not proposals:
#1 Best Overall
- Iterator helpers: a new
Iteratorglobal with associated static and prototype methods. - Set operations: common operations added to
Set.prototype. - JSON modules and import attributes: syntax and support for importing JSON modules with attributes.
- Regular-expression improvements:
RegExp.escapeand inline modifier flags. - Promise.try: a new method on
Promise. - Half-precision floating-point support:
Float16Arrayand relatedDataViewandMath.f16roundAPIs.
These additions define what the 2025 edition contains; they do not by themselves establish which runtime versions implement them. The official ECMAScript 2025 specification is the reference for the edition’s language definition.
How do JavaScript proposals become part of ECMAScript?
TC39 uses six stages to track proposals, from early exploration to readiness for inclusion in the standard. The committee approves advancement between stages, and proposal details can change along the way.
Rank #2
- Stage 0 — Strawperson: an idea is being explored.
- Stage 1: the committee examines the problem and the possible solution space.
- Stage 2: a preferred solution has been selected, but details may still change.
- Stage 2.7: a complete design is validated through tests and implementation feedback.
- Stage 3: the proposal is recommended for implementation, though compatibility concerns or implementation feedback can still prompt changes.
- Stage 4: the proposal is complete and ready for inclusion after acceptance tests, multiple compatible implementations, and implementation experience.
Stage 3 is evidence of maturity, not a promise that a feature is shipping soon or is implemented everywhere. Stage 4 is the process’s completion threshold before standard inclusion. TC39’s process document explains the stages and the committee’s criteria.
What is in the 2026 specification, and what is still being considered?
The cited 2026 specification identifies itself as ECMAScript’s seventeenth edition. Its living draft reflects the latest yearly snapshot and completed Stage 4 proposals; that status is distinct from proposals still under consideration. Consult the ECMAScript 2026 living specification for the draft itself.
TC39’s Stage 3 list provides a cross-section of current work. Examples include deferred module evaluation, source-phase imports, importing text, thenable behavior, internationalized number formatting, regular-expression buffer boundaries, and error-stack accessors. Together, these examples show work on module infrastructure and refinements to existing APIs as well as new capabilities. They are candidates, not a package of guaranteed upcoming features.
TC39 describes its Stage 3 candidates this way: “This section features proposals that are in Stage 3 of our process, which means they are close to completion.” That description indicates process maturity; it does not say when a proposal will enter an edition or become usable in a given runtime. Check the TC39 proposal tracker for current status, since proposal stages can change.
Rank #4
When might an edition be published?
TC39’s schedule is approximate, not a delivery promise for any individual proposal. The process document describes a candidate draft in February, a March milestone for Stage 4 incorporation and branching, review from April through June, and an intended submission for Ecma General Assembly ratification in July. A proposal’s appearance in the process or its stage does not guarantee inclusion in that year’s edition.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How should developers decide whether to use a new feature?
Standard status and runtime support answer different questions. A feature may be part of ECMAScript yet absent from a runtime version your users or servers still need. Conversely, an implementation detail or experimental feature should not be treated as a stable standard merely because it can be tried in one environment.
- Identify the exact feature and whether it is in a published edition or remains a proposal.
- Check current compatibility data for every browser, server runtime, or embedded environment you support.
- If your target environments do not all support it, choose an appropriate fallback or avoid relying on it.
- Recheck proposal status and runtime compatibility near release time; both can change independently.
The sources cited here explain the standard and proposal process but do not provide a cross-runtime compatibility matrix. They therefore cannot establish specific browser or Node.js support for any listed feature.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
