"browser" to "application" test builder regression: can't open CLI trace link

[Klaster1]

Command

test

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

I run per-file unit tests like so: ng test --browsers=ChromiumHeadless --include=**/page-signin.component.spec.ts. When a test fails, I click on the line link from the error stack trace to navigate to the line in test source from VSCode. After switching to "application" test builder mode, the links lead to non-existing files.

Previously, I reported a similar #29662, which was released in 19.2.0.

Minimal Reproduction

1. Create a failing unit test.
2. Run it in "application" mode.
3. Click on error line link.

Expected:
Files is opened.

Observed:
No files exists at that path, can't open it.

Exception or Error

Node.js version v23.6.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/previous-releases/.
Initial chunk files  | Names             |  Raw size
test_main.js         | test_main         |   2.96 MB | 
polyfills.js         | polyfills         | 979.40 kB | 
styles.css           | styles            | 391.17 kB | 
chunk-WYLQU5MV.js    | -                 |   2.89 kB | 
spec-id8.spec.js     | spec-id8.spec     | 656 bytes | 
jasmine-cleanup-0.js | jasmine-cleanup-0 | 519 bytes | 

                     | Initial total     |   4.34 MB

Application bundle generation complete. [20.967 seconds]

Watch mode enabled. Watching for file changes...
Ignoring framework "@angular-devkit/build-angular" from karma config file because it's not compatible with the application builder.
18 03 2025 10:52:10.922:WARN [karma]: No captured browser, open http://localhost:9876/
18 03 2025 10:52:10.939:INFO [karma-server]: Karma v6.4.4 server started at http://localhost:9876/
18 03 2025 10:52:10.940:INFO [launcher]: Launching browsers ChromiumHeadless with concurrency unlimited
18 03 2025 10:52:10.948:INFO [launcher]: Starting browser ChromiumHeadless
18 03 2025 10:52:11.514:INFO [Chrome Headless 130.0.0.0 (Windows 10)]: Connected on socket -wPzJ1r9xrR3CF2BAAAB with id 30583927
Chrome Headless 130.0.0.0 (Windows 10) id8 Format UUIDs FAILED
        Expected '108FF8BF' to be '908FF8BF'.
            at <Jasmine>
            at UserContext.<anonymous> (frontend/dist/test-out/c4c6a189-2585-4bcb-bacb-8de61fe39011/src/app/common/utils/tests/id8.spec.ts:13:57)
            at _ZoneDelegate.invoke (frontend/dist/test-out/c4c6a189-2585-4bcb-bacb-8de61fe39011/node_modules/zone.js/fesm2015/zone.js:339:158)
            at _ProxyZoneSpec.onInvoke (frontend/dist/test-out/c4c6a189-2585-4bcb-bacb-8de61fe39011/node_modules/zone.js/fesm2015/zone-testing.js:2020:33)
            at _ZoneDelegate.invoke (frontend/dist/test-out/c4c6a189-2585-4bcb-bacb-8de61fe39011/node_modules/zone.js/fesm2015/zone.js:339:46)
Chrome Headless 130.0.0.0 (Windows 10): Executed 2 of 2 (1 FAILED) (0 secs / 0.009 secs)
Chrome Headless 130.0.0.0 (Windows 10) id8 Format UUIDs FAILED
        Expected '108FF8BF' to be '908FF8BF'.
            at <Jasmine>
            at UserContext.<anonymous> (frontend/dist/test-out/c4c6a189-2585-4bcb-bacb-8de61fe39011/src/app/common/utils/tests/id8.spec.ts:13:57)
            at _ZoneDelegate.invoke (frontend/dist/test-out/c4c6a189-2585-4bcb-bacb-8de61fe39011/node_modules/zone.js/fesm2015/zone.js:339:158)
            at _ProxyZoneSpec.onInvoke (frontend/dist/test-out/c4c6a189-2585-4bcb-bacb-8de61fe39011/node_modules/zone.js/fesm2015/zone-testing.js:2020:33)
Chrome Headless 130.0.0.0 (Windows 10): Executed 2 of 2 (1 FAILED) (0.12 secs / 0.009 secs)                                                                                                                                                                                                                                                                                                                      
TOTAL: 1 FAILED, 1 SUCCESS
TOTAL: 1 FAILED, 1 SUCCESS

Your Environment

Node.js version v23.6.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/previous-releases/.

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI: 19.2.3
Node: 23.6.0 (Unsupported)
Package Manager: npm 10.9.2
OS: win32 x64

Angular: 19.2.2
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1902.3
@angular-devkit/build-angular   19.2.3
@angular-devkit/core            19.2.3 (cli-only)
@angular-devkit/schematics      19.2.3
@angular/cdk                    19.0.4
@angular/cli                    19.2.3
@angular/material               19.0.4
@schematics/angular             19.2.3
rxjs                            7.8.1
typescript                      5.6.3
zone.js                         0.15.0

Warning: The current version of Node (23.6.0) is not supported by Angular.

Anything else relevant?

Builder config:

"test": {
          "builder": "@angular-devkit/build-angular:karma",
          "options": {
            "main": "src/test.ts",
            "include": ["**/*.spec.ts"],
            "polyfills": "src/polyfills.ts",
            "tsConfig": "tsconfig.spec.json",
            "karmaConfig": "karma.conf.js",
            "builderMode": "application",
            "assets": [
              "src/favicon.ico",
              "src/assets",
              {
                "glob": "**/testing/*.png",
                "input": "src/app/",
                "output": "/test-images/"
              }
            ],
            "styles": ["src/styles.scss"],
            "stylePreprocessorOptions": {
              "includePaths": ["src/styles", "node_modules/"]
            },
            "scripts": []
          }
        },

Good output in "browser" mode:

Node.js version v23.6.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/previous-releases/.
✔ Browser application bundle generation complete.
18 03 2025 10:50:03.695:WARN [karma]: No captured browser, open http://localhost:9876/
18 03 2025 10:50:03.707:INFO [karma-server]: Karma v6.4.4 server started at http://localhost:9876/
18 03 2025 10:50:03.707:INFO [launcher]: Launching browsers ChromiumHeadless with concurrency unlimited
18 03 2025 10:50:03.710:INFO [launcher]: Starting browser ChromiumHeadless
18 03 2025 10:50:04.254:INFO [Chrome Headless 130.0.0.0 (Windows 10)]: Connected on socket 5MJxDu0aBD5ajqFmAAAB with id 77714212
Chrome Headless 130.0.0.0 (Windows 10) id8 Format UUIDs FAILED
        Expected '108FF8BF' to be '908FF8BF'.
            at <Jasmine>
            at UserContext.apply (src/app/common/utils/tests/id8.spec.ts:13:57)
            at _ZoneDelegate.invoke (node_modules/zone.js/fesm2015/zone.js:369:28)
            at ProxyZoneSpec.onInvoke (node_modules/zone.js/fesm2015/zone-testing.js:2082:39)
            at _ZoneDelegate.invoke (node_modules/zone.js/fesm2015/zone.js:368:34)
Chrome Headless 130.0.0.0 (Windows 10): Executed 2 of 2 (1 FAILED) (0 secs / 0.015 secs)
Chrome Headless 130.0.0.0 (Windows 10) id8 Format UUIDs FAILED
        Expected '108FF8BF' to be '908FF8BF'.
            at <Jasmine>
            at UserContext.apply (src/app/common/utils/tests/id8.spec.ts:13:57)
            at _ZoneDelegate.invoke (node_modules/zone.js/fesm2015/zone.js:369:28)
            at ProxyZoneSpec.onInvoke (node_modules/zone.js/fesm2015/zone-testing.js:2082:39)
Chrome Headless 130.0.0.0 (Windows 10): Executed 2 of 2 (1 FAILED) (0.111 secs / 0.015 secs)                                                                                                                                                                                                                                                                                                                     
TOTAL: 1 FAILED, 1 SUCCESS
TOTAL: 1 FAILED, 1 SUCCESS

I'm on latest Windows 11.

[cexbrayat]

I think this one is the same as #29766 which was already fixed in #29849 and should be released soon.

[alan-agius4]

Indeed, thanks @cexbrayat.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}