-
Notifications
You must be signed in to change notification settings - Fork 12k
SCSS partials not properly updating the files that import them #26390
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
Comments
I am not able to replicate this outside of stackblitz. If you are replicating it locally, can you please provide the output of |
@alan-agius4 ok, no problem. I also created a brand new app and replicated the issue outside of stackblitz (https://github.com/brianmtreese/scss-partials-issue). Angular CLI: 17.0.1 Angular: 17.0.3 Package Version@angular-devkit/architect 0.1700.1 |
Is this still an issue for you with |
Nope, it appears to be fixed now. Thanks! |
Good to hear and thank you for confirming. |
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. |
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
After updating to angular 17, when making changes to SCSS partials used in components, the changes do not take effect unless you go into the file that's importing them and trigger a save.
You can easily see this by going to the link for the reproduction, changing the color to something else, like "purple", and then saving. The color will not be changed until going into the component stylesheet (test-component.component.scss) where the variable is imported and used, and triggering a save there instead.
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/stackblitz-starters-y1ihag?file=src%2Ftest-component%2F_test-import.scss
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: