Upgrade to angular 20 (#655) #656
Open
Conversation
This file contains hidden or 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
nstdspace
force-pushed
the
master
branch
3 times, most recently
from
8045965 to
05ca2c1
Compare
adaussin-ores
approved these changes
Jul 25, 2025
|
@vlio20 when is this upgrade likely to me merged and released to NPM, I'd like to continue using your package when we upgrade to Angular V20. Cheers! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Other than updating typescirpt, I didn't find any required changes according to this list.
cache@v1is not supported anymore.constructor injectiontoinject(...)viang generate @angular/core:injectaccording to new linting settings (and usage ofinject()is recommended since angular 14)I read the contribution guidelines, but there is no
nextbranch and previous PR's all went onmaster...