ng new with sass does not build

[antoinegslight]

🐞 Bug report

Command (mark with an x)

- [x] new
- [x] build
- [x] serve
- [x] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

I don't know

Description

When choosing the sass style option when doing an ng new, the project cannot be built, served or tested. The reason is that the angular.json try to read styles.sass(which does not exist) instead of styles.scss.

🔬 Minimal Reproduction

1. ng new
2. Choose sass
3. npm install && npm build

🔥 Exception or Error

ERROR in multi ./src/styles.sass
Module not found: Error: Can't resolve '/Users/antoinegslight/Code/nexapp/efs/cliniciel-lite-boilerplate/src/styles.sass' in '/Users/antoinegslight/Code/nexapp/efs/cliniciel-lite-boilerplate'

🌍 Your Environment

Angular CLI: 7.3.1
Node: 10.11.0
OS: darwin x64
Angular: 7.2.4
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.1
@angular-devkit/build-angular     0.13.1
@angular-devkit/build-optimizer   0.13.1
@angular-devkit/build-webpack     0.13.1
@angular-devkit/core              7.3.1
@angular-devkit/schematics        7.3.1
@angular/cli                      7.3.1
@ngtools/webpack                  7.3.1
@schematics/angular               7.3.1
@schematics/update                0.13.1
rxjs                              6.3.3
typescript                        3.2.4
webpack                           4.29.0

Anything else relevant?

[AJHanekom]

Fix in angular.json

Generated with

"styles": [
              "src/styles.sass"
            ],

should be

"styles": [
              "src/styles.scss"
            ],

[AJHanekom]

#13550

[alan-agius4]

Make sure that your global cli is 7.3.1 aswell and not just the local.

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