What should I do to propose a new feature in JS

tajnur007 · January 1, 2025, 10:23am

I want to propose a new feature in the JS method. What should I do first? I have already read the ECMA262 contribution guidelines but I'm unclear. Should I create a repo first for the proposal? Or anything else?

aclaymore · January 1, 2025, 10:40am

Welcome @tajnur007

github.com

tc39/ecma262/blob/c4042979a7cdd96b663ffcc43aeee90af8d7a576/CONTRIBUTING.md#creating-a-new-proposal

### Contributing to ECMAScript

Contributors to ECMAScript and TC39 are expected to follow our [Code of Conduct](https://tc39.es/code-of-conduct/).

If you are not an Ecma member, any non-trivial contributions require signing a legal agreement with Ecma. See the section "Required Legal Agreements" below for details.

#### Issues and Pull Requests

For small changes to ECMAScript, you can contribute by filing an issue or a pull request against the current text of ECMA-262 standard in this repository.

To file an issue, go to the ecma262 [issues page](https://github.com/tc39/ecma262/issues). From there, [search](https://guides.github.com/features/issues/) in the existing issues to see if an issue already exists to track your problem. If so, add a comment to the existing issue; otherwise, [file a new issue](https://help.github.com/articles/creating-an-issue/) documenting the problem.

To make a pull request (PR), [fork](https://help.github.com/articles/fork-a-repo/) the [ecma262](https://github.com/tc39/ecma262) repository, apply changes to `spec.html`, and upload it to your fork on GitHub, using the web interface to file a pull request. Locally, to see how your change renders in HTML, run `npm install && npm run build` to build `spec.html` into an actual HTML file.

Commits in pull requests should have a first line which starts with a tag, followed by a colon, indicating which type of patch they are:
  * Normative: any changes that affect behavior required to correctly evaluate some ECMAScript source text (such as a script or module)
  * Editorial: any non-normative changes to spec text including typo fixes, changes to the document style, etc.
  * Markup: non-visible changes to markup in the spec
  * Meta: changes to documents about this repository (e.g. readme.md or contributing.md) and other supporting documents or scripts (e.g. `package.json`, design documents, etc.)

This file has been truncated. show original

Says that a good first step is to discuss the idea on this forum. You could create a gist/repo that explains the idea if that is helpful.

For an idea to become an official proposal and advance towards becoming part of the specification it must be championed by a member of TC39 at the official TC39 meetings (about 6 per year). If the company/university you are at is a member then you might be able to champion it.

What's the idea?

tajnur007 · January 1, 2025, 10:47am

Pretty clear now. Thanks for your explanation.

I think I can create a repo for the proposal first, describe the problem and possible solution(s) there, and then share it here. I will let you know after completing the proposal.

tajnur007 · January 6, 2025, 8:45am

Check it here: Replacing a string from last

Topic		Replies	Views
This forum doesn't allow to add new features, right? I have questions	7	66	September 12, 2024
How to create a proposal? I have questions proposal	3	309	November 19, 2022
Final ES2020 feature set? I have questions	9	899	April 1, 2020
Javascript Template Library 💡 Ideas	9	537	April 17, 2022
Where to ask about a feature of JS API? I have questions	3	34	November 6, 2024

What should I do to propose a new feature in JS

Related topics