Skip to content

Commit d7486be

Browse files
billyjovd3lm
authored andcommitted
content(general): use latest version of everything
1 parent 5b0a2b3 commit d7486be

File tree

2 files changed

+35
-0
lines changed

2 files changed

+35
-0
lines changed

content/general/.category

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
---
2+
title: General
3+
summary: This category summarizes best practices regarding general topics.
4+
---
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
title: use latest version of everything
3+
author:
4+
name: Billy Lando
5+
url: https://github.com/billyjov
6+
---
7+
8+
# Problem
9+
10+
The Angular team and community are continually improving the ecosystem to make it easier to build applications. Both the performance and the compiler (e.g Ivy Renderer) are constantly being improved for better web applications.
11+
12+
Angular uses semantic versioning (semver) which means they use a regular schedule of releases. This includes a major release every six month, 1-3 minor releases for each major release, and a patch release almost every week. It's important to keep up with major releases as they contain significant new features. The longer we wait to update our application, the more expensive will be a future update. Be aware, that major releases may contain breaking changes.
13+
14+
In addition, when API's get deprecated they remain present in the next two major releases until they are removed. Again, if we wait to long, it's likely that the update requires much more work. You can read more about deprecations in the [changelog](https://github.com/angular/angular/blob/master/CHANGELOG.md).
15+
16+
# Solution
17+
18+
You can follow this steps using Angular CLI:
19+
20+
- **Step 1:** Create a new feature branch
21+
- **Step 2:** Run `ng update @angular/core @angular/cli` inside your project directory
22+
- **Step 3:** Run `ng serve`, `ng test`, `ng build --prod` and make sure your app works as expected
23+
- **Step 4:** Fix update deprecations, issues, styling issues in case of Angular Material and run the previous step again
24+
- **Step 5:** merge or rebase your changes on top of the main branch
25+
26+
For more information, check out the [official update guide](https://update.angular.io/) on how to update from different versions.
27+
28+
# Resources
29+
30+
- [Keeping your Angular Projects Up-to-Date](https://angular.io/guide/updating)
31+
- [Don’t be afraid and just `ng update`!](https://itnext.io/dont-be-afraid-and-just-ng-update-1ad096147640) by Bram Borggreve

0 commit comments

Comments
 (0)