-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
☂️ Roadmap for a Rust-based compiler #114
Comments
Does that mean Linaria will finally stop trying to evaluate modules? 😮 |
When targeting Vite. Will voidzero be used? I hear a lot of talk about simplifying things re: transforms, etc. |
Is this open for contribution ? |
@nstepien nope, we will continue to evaluate modules, but the goal is to make it faster and simpler.
@paulm17 not sure that I got it. We will use OXC toolkit (parser, resolver, transformer) as our core dependency as OXC is funded by voidzero.
@brijeshb42 yes. You will see some Rust code making its path to the I plan to solve this soon and also add more clarify on the plan, but I don't want to make broken promises for now. |
@paulm17 not sure that I got it. If you hear Evan talk about how voidzero operates compared to the current paradigm. You'll understand. 😄 But regardless, you answered my question. The last time I looked at OXC was in the summer and found the transform wasn't feature complete. So much so that Next-Yak went with SWC. I've been watching this space with interest. So excited to see how this will all unfold. |
That's a shame, module evaluation is the biggest pain point with using Linaria: it leads to build failures and slow builds. |
TL;DR
We want to have nice, modern and blazing fast compiler ⚡ We aim to support Linaria & Griffel.
Dev design
TBD
Initial context could be found there, microsoft/griffel#621.
API design
We will continue to expose processors as the interface. Processors will implement actual transforms and should be written in Rust. We will continue provide plugins/loaders for bundlers.
We expect that the usage will look like that:
Roadmap
TBD
The text was updated successfully, but these errors were encountered: