chore: update dependencies to Angular 19 and other package upgrades#27
chore: update dependencies to Angular 19 and other package upgrades#27Brijeshthummar02 wants to merge 1 commit intoPSMRI:developfrom
Conversation
WalkthroughThis update modifies the Angular workspace configuration by renaming the Changes
Possibly related issues
Poem
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
package.json (1)
54-88: Review devDependencies tooling upgrades
Dev tooling (Angular CLI→19.2.x, @angular-eslint→19.4.x, TypeScript→5.8.3, Jasmine→5.7.x, Karma→6.4.x, ESLint→9.26.0, Prettier→3.5.3, etc.) has been updated. Ensure:
- ESLint configurations are compatible with the new plugin/parser versions.
- Any custom schematic or lint overrides are re-verified.
- Test runners (Karma, Jasmine) execute without deprecation warnings.
Would you like a script to regenerate/validate ESLint configs against the v19 schema?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
angular.json(2 hunks)package.json(1 hunks)
🔇 Additional comments (3)
package.json (1)
24-53: Ensure compatibility for upgraded dependencies
Core Angular packages have been bumped to v19.x and key libraries (Bootstrap^5.3.6, date-fns^4.1.0, echarts^5.6.0, jspdf^3.0.1, moment^2.30.1, ngx-cookie-service^19.1.2, rxjs^7.8.2, tslib^2.8.1, zone.js~0.15.0) may include breaking changes. Please:
- Verify peer dependency alignment (run
npm lsorng version).- Consult the Angular 19 migration guide for required code adjustments.
- Execute the full test suite and perform manual smoke tests.
angular.json (2)
127-127: Approveextract-i18nconfig key rename
Updating theextract-i18nbuilder’s option from"browserTarget"to"buildTarget"is aligned with the new CLI conventions. Please runng extract-i18nto ensure the extraction process completes without errors.
113-117:Details
✅ Verification successful
Approve
serveconfig key rename and verify no residuals
Replacing"browserTarget"with"buildTarget"in theserveconfigurations is correct for Angular CLI v19. Run this to catch any leftover entries:
🏁 Script executed:
#!/bin/bash # Search for any lingering browserTarget references rg '"browserTarget"' -n angular.jsonLength of output: 38
No residual “browserTarget” references found—changes approved
Ranrg '"browserTarget"' -n angular.jsonand confirmed there are no lingering references in the file.
|
@drtechie can you guide what's the issue over here. |
|
|
@Sneha6003 any suggestions? |
1 participant
📋 Description
Fixes: PSMRI/AMRIT#15
Please provide a summary of the change and the motivation behind it. Include relevant context and details.
✅ Type of Change
ℹ️ Additional Information
Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.
Summary by CodeRabbit