You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
When using @angular-devkit/build-angular:application in new Angular there seems to be no check for existence of css files referred from the component.
To replicate, create empty project using the latest Angular, then edit src/app/app.component.ts and change .css file path to non-existing file or any string.
After that both ng serve and ng build still run successfully without any complains/warnings.
Unit tests ng test is failing (probably because it's still using webpack)
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run ng version)
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
When using @angular-devkit/build-angular:application in new Angular there seems to be no check for existence of css files referred from the component.
To replicate, create empty project using the latest Angular, then edit
src/app/app.component.ts
and change .css file path to non-existing file or any string.After that both
ng serve
andng build
still run successfully without any complains/warnings.Unit tests
ng test
is failing (probably because it's still using webpack)Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: