feat(@angular-devkit/build-angular): use sass instead of node-sass

[alan-agius4]

BREAKING CHANGE: we no longer use node-sass by default, instead we use sass (dart-sass).

While in most cases this should not have an impact the generated code, dart sass has some differences from Ruby Sass. See https://github.com/sass/dart-sass#behavioral-differences-from-ruby-sass for more details

If you wish to use node-sass instead of sass you need to install node-sass as a dev dependency.

npm users

npm install node-sass --save-dev

yarn users

yarn add node-sass --dev

Note: for larger Sass projects to avoid this performance hit you might want to install fibers. See: https://www.npmjs.com/package/fibers

Ref: TOOL-748

[alan-agius4]

I have some doubts re the console msg, as we'll have too many console infos when starting the dev server and

1. The more we add the more people will start ignored them
2. They get invasive as there is no way to turn these off at the moment.

[alan-agius4]

@alexeagle what are your thoughts about the above? So we still do the console msg?

[filipesilva]

LGTM but I'd like @clydin to have a look, since he made most of the original changes.

[alexeagle]

The breaking change message is a good start for helping users get out of a hole. Let's see how it goes during RC

[angular-automatic-lock-bot]

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.}