Had the same issue yesterday using Angular 18. I tried upgrading to angular 19, stabilizing packages to older versions in a working environment. Still the same.

Today, I did (again), with the original problematic configuration. I compared the "npm ls" from yestarday and today. I had exactly the same output. Then, by running these commands (git bash on windows):

• rm -rf node_modules package-lock.json .angular/cache"

• npm install --force

• npm run start

And it's got to work again. Not that I changed the way to do. But it has "magically" worked. ^^"

I wonder if somehow, a patch, hidden in an previously existing version, has been made in the last hours.

Regards