You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 9, 2024. It is now read-only.
On top of all the nice optimizations done here, I think inlining JSX calls would fit nicely as a feature of this project. I've created a proof-of-concept here: https://github.com/romgrk/babel-plugin-fast-jsx, feel free to pick up anything you want from there.
The text was updated successfully, but these errors were encountered:
This is so cool and thanks for sharing. I'll think about how it can fit into this project. I believe they should remain as separate babel plugins, but it can be an extension to the unforget toolchain under the @react-unforget npm scope.
Sure, feel free to use it or not as you wish, it's released to the public domain. I unfortunately can't use either on the projects I'm working on at the moment, but if I was building the kind of stuff that benefits from unforget I'd definitely be interested in the JSX transform as well. For some cases that are mount-heavy (mounts more often that re-renders), the JSX calls do add up to a significant amount.
Sidenote but it feels so great to be able to compile React performance cliffs away. And it feels like with a few strategic breaking changes, React plus a compiler could get near SolidJS level performance.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On top of all the nice optimizations done here, I think inlining JSX calls would fit nicely as a feature of this project. I've created a proof-of-concept here: https://github.com/romgrk/babel-plugin-fast-jsx, feel free to pick up anything you want from there.
The text was updated successfully, but these errors were encountered: