Even though inlining succeeds and both out-tsc and dist folders contain properly inlined CSS, the server that's run with npm run start command is not actually inlined.
I'm not sure if this is by design, but this causes problems with my setup of SCSS, since I cannot see the proper version of the lib in the demo app. The SCSS gets imported into browser, Angular runs it through parser, and spits out a mutant monster which ain't valid CSS.
So technically it doesn't cause problems in this demo and everything works if you use CSS, but I believe this is not expected behavior -- developers expect to see their bundled lib loaded as it's bundled, not as it was written.
Ah, never mind -- I got carried away by previous development using webpack and replaced my styleUrls with .scss extension. Of course that wouldn't work in the environment.
Even though inlining succeeds and both
out-tsc
anddist
folders contain properly inlined CSS, the server that's run withnpm run start
command is not actually inlined.I'm not sure if this is by design, but this causes problems with my setup of SCSS, since I cannot see the proper version of the lib in the demo app. The SCSS gets imported into browser, Angular runs it through parser, and spits out a mutant monster which ain't valid CSS.
So technically it doesn't cause problems in this demo and everything works if you use CSS, but I believe this is not expected behavior -- developers expect to see their bundled lib loaded as it's bundled, not as it was written.