proposal-extensions
proposal-extensions copied to clipboard
tc39
Extensions proposal for ECMAScript
The semantic of `x::ext:name(` seems incompatible with tree shaking after transpile if the the `import` and `x::ext:name(` got trasnpiled individually. ``` import * as ext from 'someOtherModule' ExtInvoke(ext, 'name', x,...
The presentation at the meeting is quite a hurry and I guess many delegates (including me) didn't understand this proposal well. Based on the reaction to the meeting, I suggest...
According to [tc39/proposals](https://github.com/tc39/proposals/blob/main/stage-1-proposals.md), this proposal was last presented in November, 2020. Has there been any progress advancing to stage 2? > Conclusion/Resolution > proposal advances to stage 1 > stage...
I'm a big fan of the idea of extension functdions and accessors. I even posited the idea for virtual accessors back on the old bind operator proposal, so I'm glad...
It would be great if optional chaining was baked into the proposal: ```javascript document.querySelector("#myElement")?::let(it => { // it's safe to do things with the element here setupInteractivity(it); }); ``` Equivalent...