-
Notifications
You must be signed in to change notification settings - Fork 12
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
What's the current alternative to this ? #44
Comments
Also, I do know that this isn't your fault at all. I'm just asking if you know any alternatives, since you worked on this one ! |
There are no proposals by any W3 members for this functionality that I know of. They have directed their efforts to the Shadow DOM as a way of scoping CSS. The closest functionality that obeys the general laws of CSS would be postcss-extend-rule. You can also try its interactive demo. @coldtelling, also, I’m very sorry if I did not answer your question in another thread. It wasn’t my intention to ignore you. I hope this answer gives you some clarity, even though it may not be the answer you (or any of us) are thrilled with. |
Hey @jonathantneal Thanks for the quick reply, I really appreciate the time and resources you put in those tools. This clear things up for me. |
Maybe also postcss-mixins replicates the kind of Sass like fonctionnality most users are seeking for. |
"...the spec is yet considered deprecated and alternative solutions are being discussed."
What's the current working alternative ? I see ideas, but nothing functional. So, I think it's a bit weird to have something deprecated without an alternative.
It's a bit like you'd deprecate fossil energy instantly, then spend the rest of the year without proper electricity until there's an working alternative.
I've asked the questions on CSSnext, @jonathantneal, postcss-preset-env, etc, no answers... Maybe @pascalduez you could clarify the issue here, I'd really appreciate it.
Kindest regards !
The text was updated successfully, but these errors were encountered: