he/him 
what in particular do you not like about the way @babel/plugin-transform-runtime solves it?
Babel helpers are terrible and are responsible for bundle size bloat. In hindsight I should have added the necessary abstractions to make it easy for bundlers to insert them only once per bundle. @babel/plugin-transform-runtime was an unfortunate hackhttps://babeljs.io/docs/en/babel-plugin-transform-runtime#helper-aliasing …
-
-
-
It relies on keeping the runtime package version in sync with the Babel transform version. Results in conflicting versions, and when there's duplicate versions then the bundle bloats even more.
- 1 more reply
New conversation -
-
-
I forgive you
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It would have been cool if instead of plugins that were used after we walk over the entire AST, we had header comments that listed the transforms that were going to be used in the file itself. Right now you can’t glance at a large file and know which ten plugins matter 1/2
-
Babel macros can give us some of this, and some plugins you may actually want to run over the entire AST. Specific plugins like class properties for example would be perfect for specific files where you need them. Implicit/magic new language features just feel bad to me. 2/2
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.