@angular/build not yet compatible with angular v20

[TimoFeucht]

Describe the Bug

After updating Angular to version 20 following the NX Automate Updating Dependencies Guide starting an web application with nx serve doesn't work anymore:

Error: The current version of "@angular/build" supports Angular versions ^19.0.0 || ^19.2.0-next.0,
but detected Angular version 20.0.7 instead.

Minimal Reproduction

1. Create a Angular Project
2. Upgrade Angular to version 20 using NX Automate Updating Dependencies Guide
3. run angular project using nx serve

Expected Behavior

@angular-builders/custom-webpack supports Angular version 20.

Screenshots

Environment

Libs
- @angular/core version: 20.07
- @angular-devkit/build-angular version: 20.0.6
- @angular-builders/custom-webpack version: 19.0.1
- @nx/angular version: 21.2.3


For Tooling issues:
- Node version: 22.11.0
- yarn version: 1.22.22
- Platform:  Mac

Others:
- IDE: IntelliJ IDEA 2025.1.3 (Ultimate Edition)

Additional Context

npx nx migrate latest upgrades @angular-builders/custom-webpack to version 19.0.1 which does not support Angular version 20. There is a newer version of @angular-builders/custom-webpack (version 20.0.0) available. However, manually upgrading to this version leads to even more complex errors:

NX   Directory import 'node_modules/@angular-builders/custom-webpack/dist/dev-server' is not supported resolving 
ES modules imported from node_modules/nx/node_modules/@angular-devkit/architect/node/node-modules-architect-host.js

I'm happy to answer any upcoming questions. Cheers.

[Granga]

@TimoFeucht

I ran into a similar issue with my web project. While my local build worked with Node.js 22.17.0, the build on Cloudflare failed with Node.js 22.18.x.

After I forced Cloudflare to use Node.js 22.17.0, the build was successful. I'm not sure why the newer version is causing the build to fail, but hopefully, this information helps.

[melroy89]

I have the same issues with @angular-builders/jest, the latest version currently available is v20.0.0 (3 months ago).

However, I want to upgrade to typescript v5.9.2 and use Angular v20.3.2. However, I notice that your @angular-builders/jest@20.0.0 has dependencies with:

'@angular-devkit/build-angular': 19.2.13`

WHY!? That is wrong old version. Or maybe it is just me.

You should depend on v20.3.2 (or at least 20.x.x or higher). Right?

This is what pnpm-lock.yaml generates for me:

  '@angular-builders/jest@20.0.0(74dd0fdea3c9be3dd66c5dec1a239e26)':
    dependencies:
      '@angular-builders/common': 4.0.0(@swc/core@1.11.29(@swc/helpers@0.5.17))(@types/node@24.5.2)(chokidar@4.0.3)(typescript@5.9.2)
      '@angular-devkit/architect': 0.2003.2(chokidar@4.0.3)
      '@angular-devkit/build-angular': 19.2.13(@angular/compiler-cli@20.3.1(@angular/compiler@20.3.1)(typescript@5.9.2))(@angular/compiler@20.3.1)(@angular/localize@20.3.1(@angular/compiler-cli@20.3.1(@angular/compiler@20.3.1)(typescript@5.9.2))(@angular/compiler@20.3.1))(@swc/core@1.11.29(@swc/helpers@0.5.17))(@types/node@24.5.2)(chokidar@4.0.3)(jest-environment-jsdom@29.7.0)(jest@30.1.3(@types/node@24.5.2)(ts-node@10.9.2(@swc/core@1.11.29(@swc/helpers@0.5.17))(@types/node@24.5.2)(typescript@5.9.2)))(jiti@1.21.7)(typescript@5.9.2)(vite@7.1.5(@types/node@24.5.2)(jiti@1.21.7)(less@4.2.2)(sass@1.90.0)(terser@5.39.0)(yaml@2.8.1))(yaml@2.8.1)
      '@angular-devkit/core': 20.3.2(chokidar@4.0.3)
      '@angular/compiler-cli': 20.3.1(@angular/compiler@20.3.1)(typescript@5.9.2)
      '@angular/core': 20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1)
      '@angular/platform-browser-dynamic': 20.3.1(@angular/common@20.3.1(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1))(rxjs@7.8.2))(@angular/compiler@20.3.1)(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1))(@angular/platform-browser@20.3.1(@angular/animations@20.3.1(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1)))(@angular/common@20.3.1(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1))(rxjs@7.8.2))(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1)))
      jest: 30.1.3(@types/node@24.5.2)(ts-node@10.9.2(@swc/core@1.11.29(@swc/helpers@0.5.17))(@types/node@24.5.2)(typescript@5.9.2))
      jest-preset-angular: 14.6.0(@angular/compiler-cli@20.3.1(@angular/compiler@20.3.1)(typescript@5.9.2))(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1))(@angular/platform-browser-dynamic@20.3.1(@angular/common@20.3.1(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1))(rxjs@7.8.2))(@angular/compiler@20.3.1)(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1))(@angular/platform-browser@20.3.1(@angular/animations@20.3.1(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1)))(@angular/common@20.3.1(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1))(rxjs@7.8.2))(@angular/core@20.3.1(@angular/compiler@20.3.1)(rxjs@7.8.2)(zone.js@0.15.1))))(@babel/core@7.28.4)(@jest/transform@30.1.2)(@jest/types@30.0.5)(babel-jest@30.1.2(@babel/core@7.28.4))(jest@30.1.3(@types/node@24.5.2)(ts-node@10.9.2(@swc/core@1.11.29(@swc/helpers@0.5.17))(@types/node@24.5.2)(typescript@5.9.2)))(jsdom@26.1.0)(typescript@5.9.2)
      lodash: 4.17.21

Hence the errors I get 😢 :

apps/frontend
├─┬ @angular-devkit/build-angular 19.2.13
│ ├── ✕ unmet peer typescript@">=5.5 <5.9": found 5.9.2
│ ├── ✕ unmet peer @angular/localize@"^19.0.0 || ^19.2.0-next.0": found 20.3.1
│ ├── ✕ unmet peer @angular/compiler-cli@"^19.0.0 || ^19.2.0-next.0": found 20.3.1
│ ├── ✕ unmet peer jest@^29.5.0: found 30.1.3
│ ├─┬ @angular/build 19.2.13
│ │ ├── ✕ unmet peer typescript@">=5.5 <5.9": found 5.9.2
│ │ ├── ✕ unmet peer @angular/compiler@"^19.0.0 || ^19.2.0-next.0": found 20.3.1
│ │ ├── ✕ unmet peer @angular/localize@"^19.0.0 || ^19.2.0-next.0": found 20.3.1
│ │ └── ✕ unmet peer @angular/compiler-cli@"^19.0.0 || ^19.2.0-next.0": found 20.3.1
│ ├─┬ @ngtools/webpack 19.2.13

Again, I just want to use Angular 20.3.x together with the support TS version v5.9.x (like v5.9.2).

[just-jeb]

Libs

• @angular/core version: 20.07
• @angular-devkit/build-angular version: 20.0.6
• @angular-builders/custom-webpack version: 19.0.1
• @nx/angular version: 21.2.3

@TimoFeucht You need to use @angular-builders/custom-webpack@20

@melroy89 Jest builder v20 depends on build-angular@20. I assume a problem with your pnpm lock, but for the benefit of doubt please check what's in Jest Builder's package.json in your node_modules 🙏.

[melroy89]

yeah.. my bad.. I blame pnpm within a monorepo. After running the official angular cli to upgrade from v19 to v20, for some reason pnpm install complains about these "unmet peer" bs messages.

However, removing the node_modules and doing a clean install, you will not get these warnings at all. Maybe its just me, but I think pnpm is not fully updating all node_modules across the monorepo correctly.

EDIT: Yes. I have v20 in my package.json file: "@angular-builders/jest": "^20.0.0",

[melroy89]

yeah.. my bad.. I blame pnpm within a monorepo. After running the official angular cli to upgrade from v19 to v20, for some reason pnpm install complains about these "unmet peer" bs messages.

However, removing the node_modules and doing a clean install, you will not get these warnings at all. Maybe its just me, but I think pnpm is not fully updating all node_modules across the monorepo correctly.

EDIT: Yes. I have v20 in my package.json file: "@angular-builders/jest": "^20.0.0",

Nailed it.. I think its because I also have common "packages" in a packages directory. With are like shared js files or shared config files. For some reason I also have pnpm deps defined in those package.json files, which might conflict with my apps in the monorepo.. Anyway, its my bad.

[melroy89]

Sorry, it's me again. One last update.. So the following two "unmet peer" warnings where actually valid:

apps/frontend
├─┬ @angular-devkit/build-angular 20.3.3
│ └── ✕ unmet peer jest@^29.5.0: found 30.2.0
└─┬ @angular-builders/jest 20.0.0
  └─┬ jest-preset-angular 14.6.0
    └── ✕ unmet peer jest@^29.0.0: found 30.2.0

The problem is simple, it seems that the latest @angular-devkit/build-angular is actually not supporting Jest v30 but only v29. Related to: #1931

And the reverse is true for the latest version of jest-preset-angular (v15), which is expecting Jest v30, but that is not possible since build-angular only supports v29. I dunno maybe I shouldn't have added jest-preset-angular to the package.json to begin with.. Ow well..

[just-jeb]

Closing this as the original question has been answered: use @angular-builders/custom-webpack@20 with Angular 20.

The Jest v30 peer dependency discussion in the comments is tracked separately in #1931 (already resolved).