-
-
Notifications
You must be signed in to change notification settings - Fork 30
-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Feature: Add Lightning CSS (renamed @parcel/css) #191
Comments
I hope we get this soon. Currently |
Ah, I didn't know that, thanks for the comment! That should make things even easier 👍 |
Done #192 + docs updated (old solution will work too, but I recommend to migrate on the new function, the old was removed in the next major release) |
Thanks for the quick turnaround, appreciate it |
Feature Proposal
Devon released Lightning CSS: https://twitter.com/devongovett/status/1567898042787049473
It's the same as
@parcel/css
but now with a different name.https://lightningcss.dev/
So it'll be a matter of changing dependencies and names to support this new, old package.
I'm happy to do the work if y'all can give me directions on how you typically handle such renames. I'd imagine just removing the
parcelCssMinify
option is not ideal as it would be a breaking change. So maybe gracefully handle that option for now and fallback to the newlightningCssMinify
option then? So the options passed toparcelCssMinify
would be just passed through tolightningCssMinify
.Thanks for your work and the plugins!
The text was updated successfully, but these errors were encountered: