Repository navigation
Add target: es2022 #44571
Description
Activity
"Use Cases" ==> "Whatever" :D :D :D Maybe just remove section that is not needed/used...
Reacted by Steven and Etienne PASSOTReacted by Kagami Sascha RosylightWe would prefer to add
ES2022as a target at a later time, once the ES standard implementation is completed or unlikely to change.
The reason is that if we addES2022as a target now, we would need to implement a transformer for the target, but the proposals' implementations may still change and this would affect the transformer's implementation.Kagami Sascha Rosylight (@saschanaz)
If there's a specific problem you have related toES2022, e.g. adding something tolib.esnext.d.ts, you could create another issue just for that.once the ES standard implementation is completed or unlikely to change.
I intended to cover only finished proposals in stage 4, and thus it shouldn't be a significant issue here. (AFAIK changing behavior of stage 4 proposals in any major way will break web compatibility and thus shouldn't occur.)
Suggestion
🔍 Search Terms
es2022
✅ Viability Checklist
My suggestion meets these guidelines:
⭐ Suggestion
There are now some accepted proposals targeting ES2022.
📃 Motivating Example
Class fields, RegExp match indices, top level await
💻 Use Cases
Whatever.