The JavaScript Committee's Proposal Process
This structured approach guides ideas from their initial conception through to their potential inclusion in the JavaScript standard.
Mikhail Barash of the University of Bergen explains the TC39 process for evolving JavaScript and how developers can contribute.
This structured approach guides ideas from their initial conception through to their potential inclusion in the JavaScript standard.
The process moves an idea from being a mere concept to a final stage where it officially becomes a part of the JavaScript standard.
This integration is the final goal of the committee's rigorous review process, ensuring that new features are thoroughly vetted.
These repositories provide a transparent platform for tracking the evolution of potential JavaScript features.
The committee actively values feedback from the language community and developers, integrating it into their decision-making process.
If a developer has an idea for a new feature, they can convince a committee member to champion it. This sponsorship is crucial for the idea to be formally presented to the entire committee.
If deemed interesting, the committee will consider it for further development.
The committee will consider a proposal if they find it interesting. For those serious about contributing to JavaScript, direct engagement with the committee is an option.
An employer can join ECMA International, the standardization organization, to gain access to TC39.
This membership allows organizations to participate directly in the JavaScript development process.
However, even without officially joining the committee, individuals can still contribute significantly.
Even without officially joining the committee, individuals can still contribute. For example, developers can write tests for the Test262 testing suite, which is a vital part of the development process.
Every proposal requires a completed testing suite, a mandatory step for a proposal to advance through the TC39 process. While not everyone enjoys writing tests, it is a highly valuable contribution.
Despite some aversion to test writing, it is not as difficult as it might seem.
Mikhail Barash, from the University of Bergen in Norway, notes that writing tests is not difficult. He highlights that multiple students from his university have successfully written tests for JavaScript.
This demonstrates that even those new to the field can make meaningful contributions to the language.
Answers come from the transcript, with the exact spot cited.
Want the next article from JetBrains?
When JetBrains publishes, we'll write it up like the one you just read and email it to you.
JetBrains published 23 in the last 7 days.
Building Your First Pipeline in TeamCity CloudJetBrains6 days ago · 12:06 · 1.4K views · Created 6 days ago
JetBrains Unveils Symposium: Smarter Rust Coding AgentsJetBrains2 weeks ago · 1:58:01 · 5K views · Created 2 weeks ago
Eemeli Aro: JavaScript Needs Breaking ChangesJetBrainslast month · 5:51 · 227 views · Created last month