Unable to debug library in VS Code since 19.2.0

[acohenOT]

Command

serve

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

19.1.9

Description

With angular-cli 19.2.0, you can no longer debug libraries using Visual Studio Code.

Minimal Reproduction

git clone https://github.com/acohenOT/angular191.git
cd angular191
npm install
ng build viewer --configuration development   # this builds the library `viewer`
code .    # open project in VS Code

Add breakpoint in library component constructor

Select Run > Start Debugging

Open http://localhost:4200/viewer which loads the library component

Exception or Error

Your Environment

ng version

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

Angular CLI: 19.2.0
Node: 22.14.0
Package Manager: npm 11.2.0
OS: win32 x64

Angular: 19.2.1
... common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1902.0
@angular-devkit/build-angular   19.2.0
@angular-devkit/core            19.2.0
@angular-devkit/schematics      19.2.0
@angular/cli                    19.2.0
@schematics/angular             19.2.0
ng-packagr                      19.2.0
rxjs                            7.8.2
typescript                      5.7.3
zone.js                         0.15.0

Anything else relevant?

In package.json change cli dependencies to 19.1.9 and run npm install, then the steps above work and the breakpoint is hit.

    "@angular-devkit/build-angular": "19.1.9",
    "@angular/cli": "19.1.9",

[alan-agius4]

Thanks for opening this issue, I have looked into this and it appears that is cause by a bug in esbuild.
See: evanw/esbuild#4105