-
Notifications
You must be signed in to change notification settings - Fork 438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Angular 16 #2752
Comments
@artlowel: As discussed in today's meeting, assigning this to you for you/your team to work on. Ideally, it'd be good to understand if this is likely to take the (usual) 30-50 hours of effort, or if you anticipate it requiring additional time. |
We shortly analyzed if upgrade to Angular 16 is shorter to do for DSpace 8.0 release. So it means that third party libraries we depend on are no longer supported. Here the current list
|
Regarding
|
Something to consider for this upgrade (or the next): Karma is no longer in active development Angular is moving to Jest and we should too (it's still "experimental" in v16 though) |
I would prefer upgrading to Angular 17 since |
Angular 15 LTS ends on 2024-05-18: https://angular.io/guide/releases#actively-supported-versions
We should use this opportunity to upgrade to the latest version of Angular (v17). See https://update.angular.io/ for details
Dependencies:
As discussed in today's DevMtg, this work will be dependent on #2750 , described in more detail at https://wiki.lyrasis.org/display/DSPACE/Migration+to+Standalone+Components
Any work on this upgrade should be based off that PR 2750 because Angular 17 recommends standalone components.
Related Work:
Several past Angular upgrades can be used as a reference, if necessary
The text was updated successfully, but these errors were encountered: