feat(deps): add support for Angular 17 #106
Draft
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
|
+1, need this to upgrade Angular to v17 |
|
Angular Any progress with this pull request? |
|
Will this get published to npm for compatibility with Angular 17.x apps? |
|
Angular Any progress with this pull request? |
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.
As demonstrated in this PR, Angular 17 support can be added out of the box. Although Angular 17 does increase the requirements for TypeScript and Node versions to 5.2 and 18.13 respectively which might warrant another major release depending on your vision. Therefore I've not added it to the README.
Let me know what the vision is and I can update this draft PR accordingly.