Why spec command throwing unknown argument in Angular 18? [closed]
Closed 3 months ago.
Why spec command throwing unknown argument in Angular 18? [closed]
Closed 3 months ago.
Why spec command throwing unknown argument in Angular 18? [closed]
Closed 3 months ago.
Angular does not show new Images or Files after ng serve in Version 17 18
when creating a new angular app in Version 17,18 and start the server with ng serve, then new files in the assets folder will be shown with CANNOT GET..
when stopping the server and run ng serve again, then the files will be there.
for reproduction:
new app with:
ng new a17_test_image
then
ng serve
How to add version to index.html during ng build?
When I build an Angular 17+ project using ng build, I would like the version from package.json to be inserted into the HTML <head>. Something like:
Angular with esmodules requires my libs to import .js file
We build our own libraries and currently I am not sure what issue the libraries have but since we started to use the new angular builder
from
Angular dev server got broken with the v18 upgrade
With the Angular 17.3 -> 18.0 upgrade, the local dev server (ng serve) got broken. We use it to connect the local dev instance to our backends in the cloud, for development. There were no config changes, only dependencies and unrelated code level migrations.
In Angular 15, does ng build/ npm run build exclude spec files by default?
I’ve read different docs already but was unable to find something that explicitly states that npm run build excludes spec files by default.
Angular CLI requires a minimum Node.js
Node.js version v14.21.3 detected.
The Angular CLI requires a minimum Node.js version of v18.13.
Use –deploy-url on angular 17.3+
I’ve upgraded an angular app from angular 11 to 17, my build command on angular 11 was