Official repository tracking the evolution of the ECMAScript (JavaScript) language standard through its proposal stages.
TC39 Proposals is the official GitHub repository that tracks the development and standardization process for new JavaScript (ECMAScript) language features. It serves as a living document cataloging every proposal from initial idea through to final inclusion in the language standard, organized by the TC39 committee's stage process. It solves the problem of fragmented information by providing a single, authoritative source for understanding what new features are being considered, their current status, and their historical discussion.
JavaScript developers, library authors, educators, and browser/engine implementers who need to stay informed about the future direction of the language and potentially contribute to its evolution.
Developers choose this resource because it is the definitive, first-party source for ECMAScript proposal information directly from the standards committee (TC39). Its unique value is the comprehensive, structured, and transparent view it provides into the entire language evolution pipeline, which is not aggregated as completely elsewhere.
Tracking ECMAScript Proposals
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Maintains categorized lists of all ECMAScript proposals from Stage 0 to Finished, including inactive ones, offering a complete historical record as shown in the README's linked markdown files.
Clearly outlines the TC39 stages with links to the official process document, demystifying how JavaScript evolves through consensus-driven governance, highlighted in the 'Active proposals' section.
For active Stage 2 and Stage 3 proposals, includes authors, champions, test coverage status, and extensive meeting notes links, providing deep insights into development progress and discussions.
Provides clear onboarding instructions for transferring proposals to the TC39 organization, encouraging community participation in language evolution, as detailed in the 'Contributing to proposals' section.
Lacks information on which browsers or engines have implemented proposals, requiring users to cross-reference external sources like MDN or caniuse.com for practical usage.
The README is dominated by dense tables with technical metadata and meeting note links, making it difficult for casual users to extract actionable insights without significant effort.
Serves as a static tracker without built-in discussion forums or feedback mechanisms; users must navigate external meeting notes or proposal repos for community engagement.