DEV Community

This is why you should go Angular 9 today

Daniel Marin on February 26, 2020

I followed almost all of the events around the Angular 9 release. After reading the Angular 9 cheatsheet, reading the Angular next docs, and watchi...
Collapse
 
layzee profile image
Lars Gyrup Brink Nielsen

I've seen quite a few errors when upgrading. Like you mention in the article, we should always remember to use ng update when upgrading as well as following the migration guide.

If you experience any non-trivial errors, get in touch with me.

Collapse
 
danmt profile image
Daniel Marin This Dot • Edited

If you take a look at the video "Angular 9: Getting Ready To Update to Angular 9" from the references, they talk about everything that changed, I would recommend it as a good point of start. Anyway, as you just said, it can be hard in some projects even using ng update and following the migration guide.

Collapse
 
alvarofelipe12 profile image
Alvaro Felipe García Méndez

It's can be much complicated than that. If you use a bunch of libraries on your project you need to test (at least read how the library goes with Angular 9) in order to take that decision. But if not you can do it based on what you show in this article :P

Collapse
 
danmt profile image
Daniel Marin This Dot

The Angular Team did their best to make it easier for us. Sadly there's no way to ensure that ALL projects will be equally easy. I've updated 1 project from Angular 8 to 9 successfully with no issues.

Nevertheless, I have friends struggling for their upgrade and that's why I said "In some cases, it's as simple as running ng update @angular/core @angular/cli" instead of "It's always as simple as running ng update @angular/core @angular/cli" (:

Collapse
 
alvarofelipe12 profile image
Alvaro Felipe García Méndez

Yup, but anyway it's a good idea encouraging people to use the new version and I want to thank you for that, cause in the end any thing done could improve the actual version.

Collapse
 
noorsyyad profile image
noor

what made angular team move from ts-lint to es-lint

Collapse
 
danmt profile image
Daniel Marin This Dot • Edited

Going back to that statement I noticed I wasn't clear enough.

The Typescript team has in their roadmap improving compatibility with es-lint, once done, is very likely that ts-lint will disappear.

Given that es-lint is currently very slow in big Typescript apps, which is the common use case for Angular, the Angular Team decided to keep using ts-lint for now. I think it's a good idea to have in mind.

Collapse
 
noorsyyad profile image
noor

ok, thank you