Angular 21 support

[davidnagyworldofbooks]

This builder package is not compatible with Angular 21 and with Jest version 30.

● Validation Error:

Preset jest-preset-angular not found relative to rootDir.

Configuration Documentation: https://jestjs.io/docs/configuration

[tfuerholzer]

For me just forcing my package manager (yarn 4) to manually link against the new Angular 21 packages outright worked for me. Both for building and serving the angular application and for running jest unit tests with almost no breaking issues in a ~ 120K LoC codebase with 500 unit tests.

That being said I only have a few dozen component tests written in jest that involve angular components. Most them are unit tests that don't involve the UI and only 2 failed for after the upgrade.

Currently I have "@angular-builders/custom-esbuild": "20.0.0", "jest": "30.2.0", "jest-preset-angular": "15.0.3",. I added this section to my package.json :

"resolutions": {
    "@angular-builders/custom-esbuild": "20.0.0",
    "@angular-devkit/architect": "0.2100.0",
    "@angular-devkit/build-angular": "21.0.0",
    "@angular-devkit/core": "21.0.0",
    "@angular-devkit/schematics": "21.0.0",
    "@angular-eslint/builder": "21.0.1",
    "@angular/compiler": "21.0.0",
    "@angular-eslint/eslint-plugin": "21.0.1",
    "@angular-eslint/eslint-plugin-template": "21.0.1",
    "@angular-eslint/schematics": "21.0.1",
    "@angular-eslint/template-parser": "21.0.1",
    "@angular/build": "21.0.0",
    "@angular/cli": "21.0.0",
    "@angular/compiler-cli": "21.0.0",
    "@angular/language-service": "21.0.0",
    "@angular/animations": "21.0.0",
    "@angular/cdk": "21.0.0",
    "@angular/common": "21.0.0",
    "@angular/core": "21.0.0",
    "@angular/forms": "21.0.0",
    "@angular/platform-browser": "21.0.0",
    "@angular/platform-browser-dynamic": "21.0.0",
    "@angular/router": "21.0.0"
  }

You probably don't need all of the angular packages here but I didn't bother testing which ones you need. Probably just best to copy anything angular related in there

with nodeLinker: node-modules in the .yarnrc.yml file. After running yarn install, there should no longer be a nested nodeModules folder inside the all packages that use angular packages as a dependency. For me running ng serve using my existing configuration

"architect": {
        "build": {
          "builder": "@angular-builders/custom-esbuild:application",

outright worked.

`

[SteveW94]

Okay, the above at least indicates that the upgrade shall not require too much apart from updating the package.json dependencies, right?

It would be really awesome to soon be able to upgrade to Angular 21 here, as manually force linking in our "in production" yarn1 project is not a viable option.

Thanks for your ongoing support!

[AndreyAusianik]

@SteveW94 @tfuerholzer there are some more problems than just ability to run against angular21 somehow that author wanted to resolve with this major release (and use it to provide some breaking changes)
for example zoneless compatibility as mentioned here #1934

[just-jeb]

Hey folks, just wanted you to know that I'm aware of it, it requires some work and the support for Angular 21 will be added ASAP.
That said, please take into account that it's holidays season now, a lot of people have lower availability, myself included.

[SteveW94]

Sure thing! And thanks for the headsup nontheless 👍 🎄

[CSchulz]

Hey folks, just wanted you to know that I'm aware of it, it requires some work and the support for Angular 21 will be added ASAP. That said, please take into account that it's holidays season now, a lot of people have lower availability, myself included.

If you need some help, please let me know. I have patched my local installed version for Angular 21 and it worked for jest.
I haven't checked the other parts, yet.

[bene-starzengruber]

@just-jeb firstly, thanks for maintaining this package - much appreciated
as it is two weeks since your last comment, can you share the current state and if you have a rough timeline for the update?

[just-jeb]

WIP #1962 🙂

[sherlock1982]

Keep in mind for Jest30 also the following schema change is needed. See this

diff --git a/dist/schema.json b/dist/schema.json
index f420f4ac692337e25d045860c1dec4df34a10f0a..164cbdfb25d43f0e54f2920698b8c919f4a2f1bd 100644
--- a/dist/schema.json
+++ b/dist/schema.json
@@ -394,7 +394,7 @@
         "type": "string"
       }
     },
-    "testPathPattern": {
+    "testPathPatterns": {
       "description": "A regexp pattern string that is matched against all tests paths before executing the test.",
       "type": "array",
       "items": {