Skip to content

Upgrade Angular from 9.0.1 to 11.2.14#156

Open
devin-ai-integration[bot] wants to merge 1 commit intomasterfrom
devin/1769977321-angular-9-to-11-upgrade
Open

Upgrade Angular from 9.0.1 to 11.2.14#156
devin-ai-integration[bot] wants to merge 1 commit intomasterfrom
devin/1769977321-angular-9-to-11-upgrade

Conversation

@devin-ai-integration
Copy link

Upgrade Angular from 9.0.1 to 11.2.14

Summary

This PR upgrades the Angular application from version 9.0.1 to version 11.2.14 following the recommended incremental upgrade path (9 → 10 → 11). The upgrade includes updates to all Angular core packages, CLI tooling, TypeScript, and related dependencies.

Key changes:

  • All @angular/* packages: ~9.0.1~11.2.14
  • @angular/cli: ~9.0.2~11.2.19
  • @angular-devkit/build-angular: ~0.900.2~0.1102.19
  • typescript: ~3.7.5~4.0.8
  • zone.js: ~0.10.2~0.11.4
  • tslib: ^1.10.0^2.0.0
  • Removed deprecated extractCss option from angular.json (CSS extraction is now the default in Angular 11)
  • Switched from yarn.lock to package-lock.json

The build compiles successfully and generates both ES5 and ES2015 bundles.

Review & Testing Checklist for Human

  • Run the application locally (npm start) and verify it loads correctly in a browser - the build passes but runtime behavior was not tested
  • Test navigation to lazy-loaded routes (item details, user pages) to ensure code splitting still works
  • Verify service worker functionality if PWA features are important
  • Confirm lock file change from yarn.lock to package-lock.json is acceptable for your team's workflow
  • Check browser console for any deprecation warnings or runtime errors

Recommended test plan: Run npm install && npm start, navigate through the app's main features (feed pages, item details, user profiles), and verify no console errors appear.

Notes

  • Pre-existing lint errors were found but are unrelated to this upgrade (code style issues in the original codebase)
  • Build requires NODE_OPTIONS=--openssl-legacy-provider on newer Node.js versions due to webpack compatibility
  • Some npm EBADENGINE warnings appear during install but don't affect functionality

Link to Devin run: https://app.devin.ai/sessions/b926dc35bdcd4c4b9e5701d849f6e0fb
Requested by: Max (max@cognition.ai)

Phase 1: Angular 9 to 10 upgrade
- Updated all @angular/* packages from ~9.0.1 to ~10.2.5
- Updated @angular/cli from ~9.0.2 to ~10.2.4
- Updated @angular-devkit/build-angular from ~0.900.2 to ~0.1002.4
- Updated typescript from ~3.7.5 to ~3.9.10
- Updated zone.js from ~0.10.2 to ~0.10.3
- Updated tslib from ^1.10.0 to ^2.0.0
- Updated various dev dependencies for Angular 10 compatibility

Phase 2: Angular 10 to 11 upgrade
- Updated all @angular/* packages from ~10.2.5 to ~11.2.14
- Updated @angular/cli from ~10.2.4 to ~11.2.19
- Updated @angular-devkit/build-angular from ~0.1002.4 to ~0.1102.19
- Updated typescript from ~3.9.10 to ~4.0.8
- Updated zone.js from ~0.10.3 to ~0.11.4
- Removed deprecated 'extractCss' option from angular.json
- Updated karma from ~5.0.0 to ~6.1.0

Switched from yarn.lock to package-lock.json for npm compatibility.

Co-Authored-By: Max <max@cognition.ai>
@devin-ai-integration
Copy link
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants