Feat/migrate to angular 20

[santoshyadavdev]

This pull request introduces several updates to the project configuration and dependencies, focusing on enhancing compatibility, maintaining consistency, and improving clarity in the codebase. The most notable changes include updates to Angular and Nx dependencies, additions to the nx.json file for better type definitions, and formatting adjustments in tsconfig.base.json.

Dependency Updates:

• Updated Angular dependencies in package.json to version 20.0.x, ensuring compatibility with the latest Angular features and fixes.
• Updated Nx dependencies to version 21.2.x for improved functionality and bug fixes. [1] [2]
• Upgraded angular-eslint to version 20.1.1 and typescript to version 5.8.3 for better linting and TypeScript support.

Configuration Enhancements:

• Added type definitions for components, directives, services, and other Angular entities in nx.json, improving clarity and standardization across the project.

Formatting Improvements:

• Adjusted formatting in tsconfig.base.json for better readability, including multi-line arrays for lib and exclude properties. [1] [2]

Summary by CodeRabbit

• Chores
  • Updated Angular, Nx, and related dependencies to the latest versions for improved compatibility and performance.
  • Enhanced generator configurations to support additional Angular schematics and plugins.
  • Added new ignore pattern for migrations files.
  • Reformatted configuration files for improved readability.

[coderabbitai]

Walkthrough

The updates include changes to project configuration and dependency management files. The .gitignore file adds a new ignore pattern and adjusts formatting. nx.json expands and refines Angular and Nx generator configurations. package.json updates Angular and Nx dependencies to newer versions. tsconfig.base.json is reformatted for improved readability.

Changes

File(s)	Change Summary
.gitignore	Added migrations.json to ignored files and inserted a newline for formatting.
nx.json	Expanded Angular/Nx generator configurations with new entries and additional properties for components, services, etc.
package.json	Upgraded Angular and Nx dependencies to latest versions; switched to exact versioning for Angular packages.
tsconfig.base.json	Reformatted lib and exclude arrays to multi-line style for readability; no value changes.

Poem

In the warren, configs hop and play,
New versions bloom, old lines give way.
Generators multiply, neat and precise,
Ignore lists grow with sage advice.
Arrays stretch out, dependencies gleam—
A tidy, modern rabbit’s dream!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0c12115 and 0cdb951.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (4)

• .gitignore (1 hunks)
• nx.json (1 hunks)
• package.json (2 hunks)
• tsconfig.base.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: main

🔇 Additional comments (19)

.gitignore (2)

49-49: Add Vitest timestamp ignore pattern
Good catch adding vitest.config.*.timestamp* to ignore transient Vitest timestamp files.

---

51-51: Ignore migration artifacts
Adding migrations.json prevents checked-in migration metadata—aligns with updated Angular/Nx migration workflows.

tsconfig.base.json (2)

13-16: Reformat lib array for readability
Converting the inline lib value to a multi-line array improves clarity without changing functionality.

---

26-29: Reformat exclude array for readability
Breaking out exclude into multiple lines aligns with the style for lib and enhances maintainability.

package.json (6)

11-19: Pin Angular dependencies to exact versions
Locking to exact 20.0.4 releases ensures consistency, but consider using ^20.0.4 to automatically receive patch updates. Note that @angular/ssr remains at 20.0.3; verify if it should also be bumped to 20.0.4.

---

24-24: Update ng-packagr to match Angular 20
Pinning ng-packagr to 20.0.1 aligns with the Angular core upgrade—looks good.

---

31-32: Upgrade AnalogJS Vite Angular plugins
Updating @analogjs/vite-plugin-angular and @analogjs/vitest-angular to 1.17.1 seems correct for compatibility with Angular 20.

---

33-39: Align Angular DevKit and CLI versions
All @angular-devkit and CLI tooling are pinned to 20.0.x—this syncs with core v20.0.4.

---

42-50: Bump Nx packages to 21.2.x
Upgrading all Nx plugins to 21.2.1 (except @nx/angular-rspack at 21.1.0) improves consistency. Confirm whether @nx/angular-rspack should also upgrade to 21.2.1.

---

57-57: Review other pinned packages
Several tools (@schematics/angular, angular-eslint, nx, typescript) are now exact-pinned. Ensure this is intentional to prevent drifting between minor versions.

Also applies to: 66-66, 73-73, 77-77

nx.json (9)

102-107: Add type to component generators
Specifying "type": "component" for both @nx/angular:component and @schematics/angular:component ensures consistent file suffixes.

---

108-113: Add type to directive generators
Including "type": "directive" aligns directive naming across both Nx and Angular schematics.

---

114-119: Add type to service generators
Setting "type": "service" standardizes service file suffixes.

---

120-125: Configure SCAM generators
Adding scam and scam-directive entries with "type" ensures single-component Angular module patterns are correctly named.

---

126-131: Define typeSeparator for guards
Using "typeSeparator": "." for guard generators enforces consistent naming (e.g., foo.guard.ts).

---

132-137: Define typeSeparator for interceptors
This ensures interceptors use the same naming convention (.interceptor.ts).

---

138-143: Define typeSeparator for modules
Applying "typeSeparator": "." maintains module file suffix consistency across generators.

---

144-149: Define typeSeparator for pipes
Ensuring pipes end with .pipe.ts by default improves discoverability.

---

150-155: Define typeSeparator for resolvers
Including resolvers in the naming conventions (.resolver.ts) rounds out the generator configuration.

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch feat/migrate-to-angular-20

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[cloudflare-workers-and-pages]

Deploying devswhomove with    Cloudflare Pages

Latest commit:	0cdb951
Status:	🚫  Build failed.

View logs