-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Can't use styles input/output in CLI 6+ #11770
Comments
Hi, the option names in Angular CLI 6 have changed and are documented in https://github.com/angular/angular-cli/wiki/stories-global-styles. Instead of |
I'm facing same issue..
Let me know how to fix this issue, thanks in advance |
does this still apply for Angular CLI 7.
This documentation is deprecated but the redirected url doesn't contain information regarding this. |
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. |
Bug Report or Feature Request (mark with an
x
)Command (mark with an
x
)Versions
node --version
8.11.2npm --version
6.1.0Angular CLI: 6.1.1
Node: 8.11.2
OS: win32 x64
Angular: 6.1.0
Repro steps
In
angular.json
under projects > Client > architect > build I have this styles config with input and output:Under Angular < 6 this worked fine. But it seems the input/output feature is not a part of Angular 6?
The log given by the failure
I get an error like this when I try ng build:
Desired functionality
The use case is we want to have a
vendor.css
file for 3rd party css and a separatesite.css
for in-house css. These need to be 2 separate files, and generated as 2 separate<link>
tags in theindex.html
, instead of being bundled together in one.Please port over from Angular 5, the input/output properties and functionality of
styles
section, so that we may generate multiple css outputs.Mention any other details that might be useful
You can see use of input/output documented here:
#6899
#8831
The text was updated successfully, but these errors were encountered: