Repository navigation
styleExt troubles #7522
Description
Activity
- addedP1Impacts a large percentage of users; if a workaround exists it is partial or overly painfulImpacts a large percentage of users; if a workaround exists it is partial or overly painful
on Sep 4, 2017 - added a commit that references this issue
on Sep 5, 2017 - added 2 commits that reference this issue
on Sep 6, 2017 Still
ng g c component-nameis generating with the default "app" -prefix instead of what's defined in .angular-cli.json. Local and global @angular/cli: 1.4.1. What am I missing? Worked 5 minutes ago before updating from 1.3.2."devDependencies": {
"@angular/cli": "^1.4.1",
"@angular/compiler-cli": "^4.4.0-RC.0",
"@angular/language-service": "^4.4.0-RC.0",
"@schematics/angular": "0.0.33",
"@types/jasmine": "~2.5.54",
"@types/jasminewd2": "~2.0.3",
"@types/node": "^8.0.28",
"codelyzer": "^3.2.0",
"jasmine-core": "^2.8.0",
"jasmine-spec-reporter": "^4.2.1",
"karma": "~1.7.1",
"karma-chrome-launcher": "^2.2.0",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.3.0",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.1.2",
"ts-node": "^3.3.0",
"tslint": "^5.7.0",
"typescript": "^2.5.2"
}Apparently
ng g component component-nameworks as intended, it's just thecshorthand that's still failing to use correct prefix.- added a commit that references this issue
on Sep 12, 2017 - added 2 commits that reference this issue
on Sep 13, 2017 - added 2 commits that reference this issue
on Apr 23, 2018 angular-automatic-lock-bot commented
on Sep 7, 2019 More actionsThis 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.
- locked and limited conversation to collaborators
on Sep 7, 2019 - added 2 commits that reference this issue
on May 29, 2026
Bug Report or Feature Request (mark with an
x)Versions.
@angular/cli: 1.4.0-rc.1
node: 7.1.0
os: darwin x64
Repro steps.
first: open .angular-cli.json and modify
styleExttosass.second: ng generate component hello
Desired functionality.
it looks like that the property "styleExt" of .angular-cli.json is not being used as expected. So if you have "sass" pre-configured in .json and then want to get a new component, it will generate the style file with ".css" extension, instead of sass. until forcing --style=sass in command.