Learning the Angular update process
Angular CLI gives us a structured approach to update Angular-specific parts of our application. One type of Angular schematics is migration, which modifies our application code to comply with breaking changes. Major and minor version releases of Angular often come with migration schematics.
It is recommended to follow the update process, one major version release at a time. For example, if our application is currently using Angular View Engine version 8.2, we update it to Angular Ivy version 9.1 and verify that all aspects are behaving as expected before we take the next step to update from Angular version 9.1 to version 10.2, and so on until we reach the Angular release version we have planned to update to.
The fewer update steps we perform at a time, the easier it is to identify what went wrong when something did not go as planned.
In this section, we will first learn about the Angular Update Guide, an official web app listing step-by...
