-
-
Notifications
You must be signed in to change notification settings - Fork 197
Bundle workflow does not support css
extension in Angular styleUrls
when using scss
#4804
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
Comments
Hi @Manbearpixel, Thanks for providing a sample application! The issue is caused by the import { Component, Input } from "@angular/core";
@Component({
selector: "CreateConversationScreen, [CreateConversationScreen]",
templateUrl: "./conversation.component.html",
styleUrls: ['./conversation.component.css'] // <-- the styles file is set with .css extension
})
export class CreateConversationScreenComponent {
@Input() active: boolean;
constructor() {
}
} The Bundle workflow is not generating any css files in your app folder, it directly transpiles the replace styleUrls: ['./conversation.component.css'] with styleUrls: ['./conversation.component.scss'] You have to repeat this step for each of your components. Regarding the I also noticed that you are using an old version of
|
@DimitarTachev Thank you for taking the time to look into this! Based on your feedback, let me make sure I follow your recommended changes:
I'll give this a whirl and let you know how it goes! I had assumed that the end result (the stylesheet) had to be |
Hey @Manbearpixel , |
@rosen-vladimirov Yes, sorry! Took some time testing it out as NS 6 was just released as well so I went to test that migration. Thanks again! |
Hey @Manbearpixel , |
I've just updated the CLI and started using the new workflow to build the app. The app builds fine and typescript changes are picked up properly and compiled to JS and kicks off a build
Changes done to
scss
files however do not. This not working makes the entire switch to this build process moot for me. Does anyone have any workarounds yet?Originally posted by @Manbearpixel in #4624 (comment)
and @Manbearpixel in #4624 (comment)
The text was updated successfully, but these errors were encountered: