Angular 18 migration #201
Closed
Angular 18 migration #201
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
Migrated to angular 17 and upgraded peerdependencies of core and keepalive to angular 17 BREAKING CHANGE: 🧨 New angular version upgradation
Exposed providers array from module files
Used standalone component in docs example BREAKING CHANGE: 🧨 Remvoed regular component and App Module, Introduced AppConfig to configure necessary services
Fixed test running issue for docs
Angular 17 starts with minimum of node 18
Angular and Angular material migrated from 17 to 18
Keepalive test with new angular implementation
msibhuiyan
force-pushed
the
angular-18-migration
branch
from
838f3b8
to
fb0aa11
Compare
|
Hi, @BhuiyanSaif18. @ng-idle/core and keepalive 15 w/ Angular 17 support are out the door, again, thanks. Naturally, however, that means there are some merge conflicts since I squashed and merged. I'd rebase off the latest master and try again. |
|
@BhuiyanSaif18 can you generate a fresh PR for Angular 18 as well that will be great. Again, thanks for your help. Appreciate it a lot. |
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: