perf(@angular/cli): fix unnecessary esbuild rebuilds

[sirTomasson]

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

When using esbuild, Angular sets up a custom file watcher using esbuilds metafile inputs. Esbuild will generate define:KEY entries see https://esbuild.github.io/try/#YgAwLjI1LjMALS1kZWZpbmU6Rk9PPSd7fScgLS1tZXRhZmlsZSAtLWJ1bmRsZQBlAGVudHJ5LmpzAGNvbnNvbGUubG9nKEZPTyk. After the build is finished, the file watcher will notice that the define:KEY entries no longer exist on the file system and trigger a rebuild even though no files have changed.

Issue Number: N/A

What is the new behavior?

No rebuilds are triggered since the file watcher is no longer tracking changes to define:KEY entries.

Does this PR introduce a breaking change?

• Yes
• No

Other information

There other conditions which may also trigger a rebuilds, because the file watcher is tracking all inputs from the metafile, which are not necessarily files. This esbuild plugin example will also trigger a rebuild because esbuild will add the ns-env namespace to the metafile inputs.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[clydin]

Can you update the scope to be @angular/build instead of @angular/cli?

Otherwise, LGTM.

Thank you for the contribution.

[sirTomasson]

I changed the scope to @angular/build.

[jkrems]

The changes were merged into the following branches: main, 19.2.x, 20.0.x

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