esbuild doesn't watch for local library changes while running dev server

[marcusho21]

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

No response

Description

When working with multiple projects in an Angular workspace, running ng build --watch on the library living in the same workspace as host app, which is running using ng serve, whenever changes are being made to the library, host app doesn't trigger update when using esbuild. However, the expected behavior where host app dev server would trigger change update whenever a library gets changed works on the stable builder.

Minimal Reproduction

1. create a library and an application in the same workspace
2. update angular.json to use esbuild by update "builder": "...browser" to "builder": "...browser-esbuild"
3. run ng build --watch on the library
4. run ng serve on the host app
5. make a change to the library and save
6. host app doesn't react to the library change

Exception or Error

No response

Your Environment

Angular CLI: 16.0.5
Node: 18.16.0
Package Manager: npm 9.7.1
OS: darwin arm64

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

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1600.5
@angular-devkit/build-angular   16.0.5
@angular-devkit/core            16.0.5
@angular-devkit/schematics      16.0.5
@angular/cdk                    16.0.4
@angular/material               16.0.4
@schematics/angular             16.0.5
ng-packagr                      16.0.1
rxjs                            7.8.1
typescript                      5.0.4

Anything else relevant?

No response

[alan-agius4]

Duplicate of #25011

[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.}