-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
SASS is removing support for /deep/ #17557
Comments
Labeling this as |
@hansl This affects all Angular users that use SASS with Angular (at least if they use dart-sass or when |
We'll see how long it takes node-sass to catch up with this. I'm sending this issue to devrel to see if there's anything we can do. Thanks! |
There are references to Ping @wardbell who has had a hand in that doc. |
But we are not using it in the |
@hansl please also check the links in my initial comment. The Dart Angular and the SASS team agreed on a replacement. |
For those looking around, the replacement suggested by the AngularDart team is |
That would be quite disasterous. There is a massive number of third party modules i cannot just go and edit to use alternative replacements. |
@Ketec this is why I created the issue, so that there is time to react. |
this was resolved via b754e60 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm submitting a ...
Current behavior
Expected behavior
See also
I don't know if node-sass will keep supporting it or what SASS version Angular TS developers might use.
just to be sure it's on your radar
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Please tell us about your environment
The text was updated successfully, but these errors were encountered: