The Wayback Machine - https://web.archive.org/web/20160322113210/https://github.com/tc39/ecma262
Skip to content
Status, process, and documents for ECMA262
HTML Shell
Latest commit 7032383 @jmdyck jmdyck committed with bterlson Editorial: Refactor InitializeHostDefinedRealm()
In InitializeHostDefinedRealm(), factor out the portion
that the HTML spec appears to be interested in.
Name that portion InitializeHostDefinedRealm()
(because that seems like the most appropriate name for it),
and rename the former InitializeHostDefinedRealm to something else
(not sure what, but I'm saying RunJobs for now).

Closes #457.

README.md

ECMAScript

Current Proposals

Proposals follow this process document.

🚀 Proposal Champion Stage
SIMD.JS - SIMD APIs + polyfill John McCutchan, Peter Jensen, Dan Gohman, Daniel Ehrenberg 3
Async Functions Brian Terlson 3
Object.values/Object.entries Jordan Harband 3
String padding Jordan Harband & Rick Waldron 3
Trailing commas in function parameter lists and calls Jeff Morrison 3
Object.getOwnPropertyDescriptors Jordan Harband & Andrea Giammarchi 3
function.sent metaproperty Allen Wirfs-Brock 2
Rest/Spread Properties Sebastian Markbage 2
Shared memory and atomics Lars T Hansen 2
Function.prototype.toString revision Michael Ficarra 2
ArrayBuffer.transfer Luke Wagneer & Allen Wirfs-Brock 1
🚀 Additional export-from Statements Lee Byron 1
🚀 Class and Property Decorators Yehuda Katz and Jonathan Turner 1
Observable Kevin Smith & Jafar Husain 1
String.prototype.{trimLeft,trimRight} Sebastian Markbage 1
Class Property Declarations Jeff Morrison 1
String#matchAll Jordan Harband 1
System.global Jordan Harband 1
Asynchronous Iterators Kevin Smith 1

🚀 means the champion thinks it's ready to advance but has not yet presented to the committee.

See also the stage 0 proposals.

Contributing New Proposals

Please see Contributing to ECMAScript for the most up-to-date information on contributing proposals to this standard.

Developing the Specification

After cloning, do npm install to set up your environment. You can then do npm run build to build the spec or npm run watch to set up a continuous build. The results will appear in the out directory, which you can use npm run clean to delete.

Something went wrong with that request. Please try again.