Blog: Angular Upgrade Journey #884
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
saibonala
requested review from
bhargavigundaa,
wmrnaresh and
prasanth-reddy-wavemaker-com
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
| @@ -0,0 +1,58 @@ | |||
| --- | |||
| title: "Angular Upgrade Journey: Top 5 things to keep in mind" | |||
There was a problem hiding this comment.
Moving to which Angular version? Please mention it in the title. For example, "Ready to upgrade to Angular 16? Here's what you need to know"
| - Check [Support timelines](https://angular.io/guide/releases#support-window) for the Active and LTS versions. | ||
| - Consider upgrading Angular in incremental versions especially if the project is moving from a significantly older version. | ||
| - Angular provides comprehensive documentation on breaking changes between versions. Utilize tools like the [Angular Update Guide](https://update.angular.io/), which guides the necessary changes. Look specifically for any breaking changes or deprecated features. | ||
| - Consider creating a separate branch for the upgrade process to avoid disrupting the main development workflow until the upgrade is complete. |
There was a problem hiding this comment.
Aren't we automatically upgrading to Angular 16? Are we expecting users to create branches and so on?
| - Check for the changes in Git/npm repositories that may impact the project and adjust accordingly to avoid unexpected issues. | ||
|
|
||
| :::info | ||
| Consider supporting dependencies when upgrading to Angular Ivy from View Engine. Projects on Angular 16 and later no longer support View Engine libraries. |
There was a problem hiding this comment.
Shouldn't we specify users to be ready with all the dependencies by the proposed date?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.