Replies: 2 comments 3 replies
-
Both CSS modules and vanilla-extract compile to regular CSS files during your build. Vanilla-extract should be capable of everything CSS modules can do. That being said, if the Next team write specific code to handle CSS modules then it likely won't cater to vanilla-extract. I'd speak to Next about this if you can, maybe even suggest they support vanilla-extract OOTB 😉. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Not sure this ads some more relevant information for these kind of libraries. reactwg/react-18#108 (vanilla extract mentioned there specifically :) ) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am currently considering moving from styled components to something that has no runtime cost and that allows for better performance, the two main projects we are considering is CSS modules and Vanilla extract.
We tried both and Vanilla extract seems very very interesting, one of the things we are considering is potentially getting into blockers with the new features (pretty relevant themselves for performance as well) from nextjs. Most specifically the Layouts RFC and streaming
We were wondering if people here have some idea (given that CSS modules has already support by the information in the streaming link above) if Vanilla extract does some sort of magic that would make it difficult or that would maybe be at first incompatible with these?
Any thoughts on this would be very appreciated. Thanks! Awesome library the prototype we did with it we loved the UX and performance of it.
Beta Was this translation helpful? Give feedback.
All reactions