Quoting Tan's "Closing" section at Creating custom JavaScript syntax with Babel
The steps we've gone through above is similar to part of the TC39 proposal process when defining a new JavaScript specification. When proposing a new specification, the champion1 of the proposal usually write polyfills or forked out babel to write proof-of-concept demos. As you've seen, forking a parser or writing polyfills is not the hardest part of the process, but to define the problem space, plan and think through the use cases and edge cases, and gather opinions and suggestions from the community. To this end, I am grateful to the proposal champions, for their effort in pushing the JavaScript language forward.
- See repo https://github.com/tc39/proposals for the list of proposals and have a look at the org: https://github.com/tc39.
- The tc39 web is https://tc39.es/
- To follow the discussions see https://es.discourse.group
- See section ECMAScript proposals for the list of ECMAScript proposals supported by Babel Parser.
- See section Language Extensions for the flow, jsx, typescript and v8x extensions suppor* TC39 Panel - JavaScript Inside Out How Your Favorite Programming Language Is Being Created?
Here is a challenge for you:
- TC39 Agendas: A repo with a folder per year and markdowns 01.md ... for each meeting. For instance https://github.com/tc39/agendas/blob/main/2017/01.md and see the slides by Gabriel Isenberg (Champion at the time) for the Null Propagation Operator at Google Slides
- TC39 Panel - JavaScript Inside Out How Your Favorite Programming Language Is Being Created? Youtube. June 2023.
- https://es.discourse.group
Footnotes
-
The person who is responsible for the ES proposal. Either the champion or a co-champion must be a member of TC39. See https://www.proposals.es/stages/stage1 ↩