Skip to content
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

Lightning CSS as parser over PostCSS? #6

Open
asuh opened this issue Jun 7, 2024 · 1 comment
Open

Lightning CSS as parser over PostCSS? #6

asuh opened this issue Jun 7, 2024 · 1 comment

Comments

@asuh
Copy link
Owner

asuh commented Jun 7, 2024

Vite uses PostCSS by default, and that's great, but I'm quite curious about Lightning CSS as well. I think there might be advantages as the codebase grows.

I'd need to find out if Lightning CSS changes the /node_modules/ directory to replace PostCSS with Lightning CSS.

I'd also need to see the output of the build since it'll replace using ESBuild for CSS.

Reference

@asuh
Copy link
Owner Author

asuh commented Nov 19, 2024

Fndings so far:

  1. Lightning CSS doesn't modify the amount of packages in /node_modules/ so it's not really a way to shrink down the dependencies ultimately
  2. There's no speed advantage during the dev workflow, it feels similar to PostCSS
  3. Any transpiling advantage is too small for average or small codebases

I'm leaning toward not enabling by default, but maybe I'll leave in some commented out code for others to enable, if they want

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant