Upgrade Angular from v9.0.1 to v19 #92
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
- Upgraded from Angular 9.0.1 to Angular 12.2.18 - Upgraded through intermediate versions: 9 → 10 → 11 → 12 - Updated all @angular/* packages to version 12 - Updated zone.js to 0.11.x - Updated tslint to version 6 - Removed deprecated options from angular.json - Updated TypeScript compiler options in tsconfig.json - Updated relativeLinkResolution in app.routes.ts - Renamed browserslist to .browserslistrc - Removed emitDecoratorMetadata from tsconfig.json - All automated migrations completed successfully - Production build verified and working Co-Authored-By: Kevin Tang <kevin.tang513@gmail.com>
- Upgraded from Angular 12.2.18 to Angular 15.2.10 - Upgraded through intermediate versions: 12 → 13 → 14 → 15 - Updated all @angular/* packages to version 15 - Updated TypeScript from 4.3.5 to 4.9.5 - Updated zone.js to 0.11.x - Updated .gitignore to include '.angular/cache' - Removed deprecated options from angular.json - Removed relativeLinkResolution from router config - Updated TypeScript compilation target to ES2022 - Removed IE-specific polyfills (no longer needed) - Updated test configuration for Angular 13+ teardown behavior - Changed dependency version prefix from '~' to '^' - All automated migrations completed successfully - Production build verified and working Co-Authored-By: Kevin Tang <kevin.tang513@gmail.com>
Co-Authored-By: Kevin Tang <kevin.tang513@gmail.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
Upgrade Angular from v9.0.1 to v19
Summary
Upgraded the Angular application from version 9.0.1 to 19.2.15 (latest) using a milestone-based approach to handle the 10 major version jump. The upgrade was completed in three milestones:
Milestone 1: Angular 9 → 12
Milestone 2: Angular 12 → 15
Milestone 3: Angular 15 → 19
standalone: falsedeclarations to all components (Angular 19 migration)All builds verified successfully at each version milestone. The app now uses:
Review & Testing Checklist for Human
This is a major upgrade spanning 10 versions with limited automated testing. Please verify:
yarn buildwith production configuration and verify output is correctyarn start) and manually test:Notes
Build Configuration Changes:
aot,extractCss(now defaults)browserTarget→buildTarget(Angular 12+ standard)Known Limitations:
Dependencies:
rxjs-compatis still included (consider removal in future if not needed)^prefix for semver rangesLink to Devin run: https://app.devin.ai/sessions/35a96f7989fb4ad08b6459dc270b2f46
Requested by: Kevin Tang (@kevintang513)