-
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
CSS imports do not work for component CSS #4285
Labels
P1
Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Comments
filipesilva
added
command: build
P1
Impacts a large percentage of users; if a workaround exists it is partial or overly painful
labels
Jan 30, 2017
change file extension to scss it works well styleUrls: ['./test.scss'], in my test.scss file I use |
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this issue
Feb 13, 2017
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this issue
Feb 13, 2017
hansl
pushed a commit
that referenced
this issue
Feb 14, 2017
asnowwolf
pushed a commit
to asnowwolf/angular-cli
that referenced
this issue
Apr 12, 2017
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
P1
Impacts a large percentage of users; if a workaround exists it is partial or overly painful
In
beta.26
, the following results in a runtime error:For global styles,
css-loader
is what resolves imports currently. Component styles hadcss-loader
added in an incorrect way, which resulted in broken CSS (fixed by @clydin in #3511).Using
'exports-loader?module.exports.toString()'
together withcss-loader
fixes this bug, but I know @clydin is currently working incss-loader
replacement functionality via PostCSS plugins for imports, which also solves the problem so it's better to wait for that solution.The text was updated successfully, but these errors were encountered: