Skip to content

feat(angular): support angular v22#35851

Draft
leosvelperez wants to merge 8 commits into
masterfrom
angular-v22
Draft

feat(angular): support angular v22#35851
leosvelperez wants to merge 8 commits into
masterfrom
angular-v22

Conversation

@leosvelperez

Copy link
Copy Markdown
Member

No description provided.

@leosvelperez leosvelperez self-assigned this Jun 2, 2026
@netlify

netlify Bot commented Jun 2, 2026

Copy link
Copy Markdown

Deploy Preview for nx-docs ready!

Name Link
🔨 Latest commit 7598ed1
🔍 Latest deploy log https://app.netlify.com/projects/nx-docs/deploys/6a284b520c1cf6000819322c
😎 Deploy Preview https://deploy-preview-35851--nx-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jun 2, 2026

Copy link
Copy Markdown

Deploy Preview for nx-dev ready!

Name Link
🔨 Latest commit 7598ed1
🔍 Latest deploy log https://app.netlify.com/projects/nx-dev/deploys/6a284b52b96f04000930457b
😎 Deploy Preview https://deploy-preview-35851--nx-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@nx-cloud

nx-cloud Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

View your CI Pipeline Execution ↗ for commit 7598ed1

Command Status Duration Result
nx affected --targets=lint,test,build,e2e,e2e-c... ✅ Succeeded 28m 43s View ↗
nx run-many -t check-imports check-lock-files c... ✅ Succeeded 5s View ↗
nx-cloud record -- pnpm nx-cloud conformance:check ✅ Succeeded 1m View ↗
nx build workspace-plugin ✅ Succeeded <1s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded 20s View ↗
nx-cloud record -- nx format:check ✅ Succeeded 19s View ↗
nx affected -t e2e-macos-local --parallel=1 --b... ✅ Succeeded 34m 25s View ↗

☁️ Nx Cloud last updated this comment at 2026-06-09 18:05:08 UTC

@leosvelperez leosvelperez force-pushed the angular-v22 branch 2 times, most recently from f861bb9 to 1ff1267 Compare June 3, 2026 09:30
nx-cloud[bot]

This comment was marked as outdated.

@PieterjanDeClippel

PieterjanDeClippel commented Jun 3, 2026

Copy link
Copy Markdown

@leosvelperez Angular 22 release has finally arrived 15 minutes ago

But it seems that nx still relies on the baseUrl, which is deprecated in TS6

● All libraries build now (the trailing-comma fix). But I've hit a genuine conflict around your "remove baseUrl" directive that needs your call. Let me lay it out:

  The constraint matrix (TS6 + nx 22):
  - ./-relative paths, no baseUrl (current): libraries build ✓, but the demos fail — nx's nxViteTsPaths needs baseUrl to resolve workspace @example/* imports, so Rollup can't
  bundle them.
  - non-./ paths + baseUrl (original style): demos resolve ✓, but every tsc-based build errors TS5101 (baseUrl deprecated) ✗.
  - baseUrl + ignoreDeprecations: "6.0": everything works ✓ — and almost certainly also fixes the r-video-player .d.ts issue (vite-plugin-dts would emit the bare
  @example/player-provider specifier instead of the broken relative source path).

  So nx 22's toolchain (nxViteTsPaths, vite-plugin-dts) is fundamentally built around baseUrl; TS6 deprecates it. There's no config that satisfies "no baseUrl AND no
  ignoreDeprecations" with nx 22.

@socket-security

socket-security Bot commented Jun 4, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @angular-devkit/build-angular is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: packages/angular/package.jsonnpm/@angular-devkit/build-angular@22.0.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@angular-devkit/build-angular@22.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm @angular/build is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: packages/angular-rspack-compiler/package.jsonnpm/@angular/build@22.0.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@angular/build@22.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@softworckx

Copy link
Copy Markdown

Is there an estimated timeline for when this version might be released? 🙏🏼

@robertIsaac

Copy link
Copy Markdown
Contributor

Is there an estimated timeline for when this version might be released? 🙏🏼

I only see drop support for Angular 19 in this PR, so I think they still need more time

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

@leosvelperez leosvelperez force-pushed the angular-v22 branch 2 times, most recently from f5bd8a6 to 4c53e04 Compare June 8, 2026 15:06
leosvelperez and others added 2 commits June 9, 2026 09:01
## Current Behavior

`@nx/angular` supports Angular 19, 20, and 21.

## Expected Behavior

Drops support for Angular 19; the minimum supported version is now 20.
Removes the Angular 19 version mappings, compatibility branches, SSR
templates, and the v19-only `serverRouting` option.

> [!NOTE]
> Part of the Angular v22 upgrade. This targets the `angular-v22`
integration branch rather than `master`.

<!-- polygraph-session-start -->
---
[View session information
↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/angular-v22.0.0-rc.2-5a2c66d4)
<!-- polygraph-session-end -->

---------

Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
## Current Behavior

Nx installs and generates TypeScript 5.9. Generated tsconfigs use
options that are hard errors on TypeScript 6 (`moduleResolution: node`,
`esModuleInterop: false`, etc.), so workspaces cannot move to TS 6.

## Expected Behavior

Nx defaults to TypeScript ~6.0.3 while still supporting >=5.8.0.
Generators emit version-appropriate config (`bundler` resolution on TS 6
workspaces, `node10` on TS 5.x), an update migration moves eligible
workspaces to TS 6 and keeps their existing tsconfigs compiling via
`ignoreDeprecations: "6.0"`, and Remix workspaces stay on TS 5.x
(generators error on TS 6 and pin 5.x on fresh setups). The repo itself
builds and tests on TS 6.0.3.

> [!NOTE]
> The Angular 22 toolchain bump and Angular-specific tsconfig fixes land
as a follow-up on this branch. Until then, the Angular 21.2 toolchain
peers `typescript <6.0`, so peer warnings are expected in the interim.

<!-- polygraph-session-start -->
---
[View session information
↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/nxc-4501-e52da5bd)
<!-- polygraph-session-end -->

---------

Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
nx-cloud[bot]

This comment was marked as outdated.

leosvelperez and others added 2 commits June 9, 2026 17:08
Bumps angular-eslint to v22 (and its now-required @typescript-eslint v8)
for Angular 22 workspaces, and aligns the repo eslint catalog to
^22.0.0.

<!-- polygraph-session-start -->
---
[View session information
↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/angular-v22-76d725d8)
<!-- polygraph-session-end -->
nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

@nx-cloud nx-cloud Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nx Cloud has identified a flaky task in your failed CI:

🔂 Since the failure was identified as flaky, we triggered a CI rerun by adding an empty commit to this branch.

Nx Cloud View detailed reasoning in Nx Cloud ↗


🎓 Learn more about Self-Healing CI on nx.dev

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.

4 participants