We've been from 8 to 9 to 10. In retrospect both 8 and 9 had yucky behavior with NPM Modules. I don't know why, but I could spend a week or two anytime I needed an update. I wrote some articles about this, and even opened 2 bugs with Angular team.
Recommendation: Angular 10 had so many fixes in it that it just seemed to do away with the NPM problems. I was forced to deep dive into NPM module system before, which was ultimately good, but now, it's just working as well as .NET compiles work. They must have shored up the Angular CLI as ng update just works if you follow their site recommendations. Since the upgrade (without measurement) The pages just feel a lot more snappy.
We've been from 8 to 9 to 10. In retrospect both 8 and 9 had yucky behavior with NPM Modules. I don't know why, but I could spend a week or two anytime I needed an update. I wrote some articles about this, and even opened 2 bugs with Angular team.
Get rid of NGModule
And this one which tells all about Angular Compiler Error messages, each of which I hit during those three upgrades.
Angular's horrible compiler error messages
Recommendation: Angular 10 had so many fixes in it that it just seemed to do away with the NPM problems. I was forced to deep dive into NPM module system before, which was ultimately good, but now, it's just working as well as .NET compiles work. They must have shored up the Angular CLI as ng update just works if you follow their site recommendations. Since the upgrade (without measurement) The pages just feel a lot more snappy.
Angular 10 is golden in my book.
Thanks for sharing!