Swap postcss for lightningcss #11040
Replies: 5 comments 5 replies
-
Why might one prefer Lightning CSS over PostCSS? Aside from its performance claims, which seems to be the basis of that project's branding. Generally a tool written in Rust is likely to be more performant and type-safe than Node.js (assuming eqivalent code quality), so performance in itself doesn't seem like a great selling point. I neither agree nor disagree, but PostCSS is very established and FWIW this is the first time I've heard of Lightning CSS, so I'd be interested to hear a good argument for this particular Rust-based alternative to PostCSS. |
Beta Was this translation helpful? Give feedback.
-
Already planning on it — it's already integrated in |
Beta Was this translation helpful? Give feedback.
-
I'm exected about this and interested in when'll it be stable? Cause vite with lightning is almost coming |
Beta Was this translation helpful? Give feedback.
-
Anything related to performance is precious. Let's not forget that Tailwind code compiles to 10K while Bootstrap is 70K. One of the major reasons we migrated to Tailwind in the first place was its performance. As we write more and more code, we need to reduce the compilation and bundling time, and file size over the network. We are also very excited to hear that the Tailwind team has a plan for Lightning CSS. |
Beta Was this translation helpful? Give feedback.
-
Was this launched in v3.4 as said in a previous tailwind blog post about Oxide? |
Beta Was this translation helpful? Give feedback.
-
It would be cool if tailwind was no longer dependent on postcss, a potential alternative is lightning css which should be faster. https://lightningcss.dev/ it has built in prefixing as well so handles the autoprefixer use case too.
Beta Was this translation helpful? Give feedback.
All reactions