-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
CSS @apply Rule support #871
Comments
My understanding is that Looking at the stack trace, it should be straightforward to fix it so that it just ignores |
I agree, in that sense Svelte should adhere to the "robustness principle". Anyway thank you very much for the fix. |
handle unknown at-rules that are declaration-like
Released 1.40.2 with the fix |
This is just to let you know you that my joy to finally see
I hope that sooner or later, better times will come with the advent of CSS Shadow Parts. |
Me too! |
@martinandert @Rich-Harris Hello what about this ? Still see this message.
|
The
@apply
rule isn't currently supported by any browser but in my opinion it is a very useful feature in order to keep styles reusable by sharing global custom sets down to scoped styles.To overcome the lack of support of custom sets, I tried to use cascading mechanism between components but I encountered several troubles to avoid unwanted style overrides with root level shared classes.
At the end I found a way to process styles with PostCSS/nextcss but when I try to use the
@apply
rule in a component I get the following error: Cannot read property 'toLowerCase' of undefined.I was wondering if it is a known limitation of the parser and if there is a way to fix it.
The text was updated successfully, but these errors were encountered: