Closed Tim-arts closed 3 years ago
You should use @use '~@angular/material' as mat;
instead of @use '~@angular/material/theming' as mat;
. Also in general you should use ng update
to update your @angular
packages, because it has automated migrations that account for breaking changes like this one.
I was using @use '~@angular/material' as mat;
but changed for @use '~@angular/material/theming' as mat;
since it was not working.
ng update
output ->
Using package manager: 'npm'
Collecting installed dependencies...
Found 25 dependencies.
We analyzed your package.json and everything seems to be in order. Good work!
But I still have the error.
Okay, I've ran the build compilation and it passed successfully, so it seems that the error comes from the way the watcher works and not from the Angular side. I'm closing this issue as it's not Angular relative anymore, will open an issue on the Jetbrains support website.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
Steps to reproduce:
Expected Behavior
The watcher runs and compiles successfully the SCSS file
Actual Behavior
I'm on Webstorm, which set up a SASS watcher to compile the SCSS files located in my project folder. While running the watcher it fails:
Environment
Additionnal information
I've tried the solution indicated right there but it doesn't work as well