ECMAScript is a JavaScript standard developed by Ecma International. Since 2015, major versions have been published every June.
ECMAScript 2025, the 16th and current version, was released in June 2025.
In June 2004, Ecma International published ECMA-357 standard, defining an extension to ECMAScript, known as ECMAScript for XML (E4X). Ecma also defined a "Compact Profile" for ECMAScript â known as ES-CP, or ECMA 327 â that was designed for resource-constrained devices, which was withdrawn in 2015.
The proposed 4th edition of ECMA-262 (ECMAScript 4 or ES4) would have been the first major update to ECMAScript since the 3rd edition was published in 1999. The specification (along with a reference implementation) was originally targeted for completion by October 2008. The first draft was dated February 1999. An overview of the language was released by the working group on 23 October 2007.
By August 2008, the ECMAScript 4th edition proposal had been scaled back into a project code named ECMAScript Harmony. Features under discussion for Harmony at the time included:
The intent of these features was partly to better support programming in the large, and to allow sacrificing some of the script's ability to be dynamic to improve performance. For example, Tamarin â the virtual machine for ActionScript, developed and open-sourced by Adobe â has just-in-time compilation (JIT) support for certain classes of scripts.
In addition to introducing new features, some ES3 bugs were proposed to be fixed in edition 4. These fixes and others, and support for JSON encoding/decoding, have been folded into the ECMAScript, 5th Edition specification.
Work started on Edition 4 after the ES-CP (Compact Profile) specification was completed, and continued for approximately 18 months where slow progress was made balancing the theory of Netscape's JavaScript 2 specification with the implementation experience of Microsoft's JScript .NET. After some time, the focus shifted to the ECMAScript for XML (E4X) standard. The update has not been without controversy. In late 2007, a debate between Eich, later the Mozilla Foundation's CTO, and Chris Wilson, Microsoft's platform architect for Internet Explorer, became public on a number of blogs. Wilson cautioned that because the proposed changes to ECMAScript made it backwards incompatible in some respects to earlier versions of the language, the update amounted to "breaking the Web", and that stakeholders who opposed the changes were being "hidden from view". Eich responded by stating that Wilson seemed to be "repeating falsehoods in blogs" and denied that there was attempt to suppress dissent and challenged critics to give specific examples of incompatibility. He pointed out that Microsoft Silverlight and Adobe AIR rely on C# and ActionScript 3 respectively, both of which are larger and more complex than ECMAScript Edition 3.
Yahoo, Microsoft, Google, and other 4th edition dissenters formed their own subcommittee to design a less ambitious update of ECMAScript 3, tentatively named ECMAScript 3.1. This edition would focus on security and library updates, with a large emphasis on compatibility. After the aforementioned public sparring, the ECMAScript 3.1 and ECMAScript 4 teams agreed on a compromise: the two editions would be worked on, in parallel, with coordination between the teams to ensure that ECMAScript 3.1 remains a strict subset of ECMAScript 4 in both semantics and syntax.
However, the differing philosophies in each team resulted in repeated breakages of the subset rule, and it remained doubtful that the ECMAScript 4 dissenters would ever support or implement ECMAScript 4 in the future. After over a year since the disagreement over the future of ECMAScript within the Ecma Technical Committee 39, the two teams reached a new compromise in July 2008: Brendan Eich announced that Ecma TC39 would focus work on the ECMAScript 3.1 (later renamed to ECMAScript, 5th Edition) project with full collaboration of all parties, and vendors would target at least two interoperable implementations by early 2009. In April 2009, Ecma TC39 published the "final" draft of the 5th edition and announced that testing of interoperable implementations was expected to be completed by mid-July. On 3 December 2009, ECMA-262 5th edition was published.
Additions include JSON, <code>String.trim()</code> to easily remove whitespaces surrounding a string (<code>" example "</code> to <code>"example"</code>), <code>String.charAt()</code> to return a single character from a given position in a string, and <code>Array.isArray()</code>. A comma after the final pair of values in an object (<code>var example = { "property1":"value1", "property2":"value2", }</code>) also no longer causes a syntax error.
The 6th edition, ECMAScript 6 (ES6) and later renamed to ECMAScript 2015, was finalized in June 2015. This update adds significant new syntax for writing complex applications, including class declarations (), ES6 modules like , but defines them semantically in the same terms as ECMAScript 5 strict mode. Other new features include iterators and loops, Python-style generators, arrow function expression (), <code>let</code> keyword for local declarations, <code>const</code> keyword for constant local declarations, binary data, typed arrays, new collections (maps, sets and WeakMap), promises, number and math enhancements, reflection, proxies (metaprogramming for virtual objects and wrappers) and template literals using backticks (<code>`</code>) for multi-line strings without escape characters. The complete list is extensive. As the first "ECMAScript Harmony" specification, it is also known as "ES6 Harmony".
The 7th edition, or ECMAScript 2016, was finalized in June 2016. Its features include exponentiation operator <code>**</code> for numbers, <code>await</code>, <code>async</code> keywords for asynchronous programming (as a preparation for ES2017), and the function. The exponentiation operator is equivalent to , but provides a simpler syntax similar to languages like Python, F#, Perl, and Ruby. <code>async</code> / <code>await</code> was hailed as an easier way to use promises and develop asynchronous code.
The 8th edition, or ECMAScript 2017, was finalized in June 2017. Its features include the , and functions for easy manipulation of Objects, <code>async</code> / <code>await</code> constructions that use generators and promises, and additional features for concurrency and atomics. It also includes <code>String.prototype.padStart()</code>.
The 9th edition, or ECMAScript 2018, was finalized in June 2018. New features include the spread operator and rest parameters (<code>...</code>) for object literals, asynchronous iteration, <code>Promise.prototype.finally</code> and additions to RegExp.
The spread operator allows for the easy copying of object properties, as shown below.
The 10th edition, or ECMAScript 2019, was published in June 2019. Added features include, but are not limited to, <code>Array.prototype.flat</code>, <code>Array.prototype.flatMap</code>, changes to <code>Array.sort</code>, and <code>Object.fromEntries</code>.
is now guaranteed to be stable, meaning that elements with equal sorting keys will not change relative order before and after the sort operation. <code>Array.prototype.flat(depth=1)</code> flattens an array to a specified depth, meaning that all subarray elements (up to the specified depth) are concatenated recursively.
Another notable change is that so-called catch binding became optional.
The 11th edition, or ECMAScript 2020, was published in June 2020. In addition to new functions, this version introduces a <code>BigInt</code> primitive type for arbitrary-sized integers, the nullish coalescing operator, and the globalThis object.
BigInts are created either with the constructor or with the syntax , where "n" is placed after the number literal. BigInts allow the representation and manipulation of integers beyond , while Numbers are represented by a double-precision 64-bit IEEE 754 value. The built-in functions in are not compatible with BigInts; for example, exponentiation of BigInts must be done with the operator instead of .
The nullish coalescing operator, , returns its right-hand side operand when its left-hand side is or . This contrasts with the operator, which would return for all "falsy" values, such as the ones below.
Optional chaining makes it possible to access the nested properties of an object without having an AND check at each level. An example is . If any of the properties are not present, will be .
The 12th edition, ECMAScript 2021, was published in June 2021. This version introduces the method for strings; , a promise combinator that short-circuits when an input value is fulfilled; , a new error type to represent multiple errors at once; logical assignment operators (, , <code>||=</code>); , for referring to a target object without preserving it from garbage collection, and , to manage registration and unregistration of cleanup operations performed when target objects are garbage collected; separators for numeric literals (); and was made more precise, reducing the number of cases that result in an implementation-defined sort order.
The 13th edition, ECMAScript 2022, was published in June 2022. This version introduces top-level , allowing the keyword to be used at the top level of modules; new class elements: public and private instance fields, public and private static fields, private instance methods and accessors, and private static methods and accessors; static blocks inside classes, to perform per-class evaluation initialization; the syntax, to test for presence of private fields on objects; regular expression match indices via the flag, which provides start and end indices for matched substrings; the property on objects, which can be used to record a causation chain in errors; the method for Strings, Arrays, and TypedArrays, which allows relative indexing; and , a convenient alternative to .
The 14th edition, ECMAScript 2023, was published in June 2023. This version introduces the <code>toSorted</code>, <code>toReversed</code>, <code>with</code>, <code>findLast</code>, and <code>findLastIndex</code> methods on <code>Array.prototype</code> and <code>TypedArray.prototype</code>, as well as the <code>toSpliced</code> method on <code>Array.prototype</code>; added support for <code>#!</code> shebang comments at the beginning of files to better facilitate executable ECMAScript files; and allowed the use of most Symbols as keys in weak collections.
The 15th edition, ECMAScript 2024, was published in June 2024. This version introduces the <code>Object.groupBy</code> and <code>Map.groupBy</code> static methods, <code>Promise.withResolvers</code>, various set operations on <code>Set.prototype</code>, and the <code>/v</code> unicode flag for regular expressions.
The <code>Object.groupBy</code> and <code>Map.groupBy</code> methods group an iterable collection using the return value of a provided callback function.<code>Promise.withResolvers</code> provides a simple way to get a promise's resolve and reject functions directly without having to assign them in the constructor.The <code>/v</code> flag in regular expressions is simply an improved version of the <code>/u</code> flag, but as it makes backwards-incompatible changes it had to be introduced as a new flag.
The 16th edition of ECMAScript released in 2025. It adds the following:
ES.Next is a dynamic name that refers to whatever the next version is at the time of writing. ES.Next features include finished proposals (aka "stage 4 proposals") as listed at finished proposals that are not part of a ratified specification. The language committee follows a "living spec" model, so these changes are part of the standard, and ratification is a formality.