chore(deps): bump esbuild, @angular/build and ng-packagr

[dependabot]

Bumps esbuild to 0.28.1 and updates ancestor dependencies esbuild, @angular/build and ng-packagr. These dependencies need to be updated together.

Updates esbuild from 0.27.7 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Commits

• bb9db84 publish 0.28.1 to npm
• 9ff053e security: add integrity checks to the Deno API
• 0a9bf21 enforce non-negative size in gzip parser
• e2a1a71 security: forbid \\ in local dev server requests
• 83a2cbf fix #4482: don't inline using declarations
• 308ad74 fix #4471: renaming of nested var declarations
• f013f5f fix some typos
• aafd6e4 chore: fix some minor issues in comments (#4462)
• 15300c3 follow up: cjs evaluation fixes
• 1bda0c3 fix #4461, fix #4467: esm evaluation fixes
• Additional commits viewable in compare view

Updates @angular/build from 21.2.18 to 22.0.5

Release notes

Sourced from @​angular/build's releases.

22.0.5

@​schematics/angular

Commit	Description
	remove unused app tsconfig outDir

@​angular/cli

Commit	Description
	gracefully handle package manager errors in command handler
	respect release age policy in update bootstrapping logic

@​angular-devkit/build-angular

Commit	Description
	prevent OS command injection in ssr-dev-server builder

@​angular/build

Commit	Description
	auto-inject localize/init in library unit tests
	inherit preserveSymlinks option from build target in unit-test builder
	load zone.js dynamically for library unit tests
	scope createRequire module resolution using paths to prevent parent paths

@​angular/ssr

Commit	Description
	preserve response headers during redirect

22.0.4

@​angular/build

Commit	Description
	aggregate parallel worker performance timings on the main thread
	dispose builder result context early in non-watch mode

22.0.3

@​schematics/angular

Commit	Description
	remove default workspace vscode mcp.json configuration

22.0.2

@​angular/cli

Commit	Description
	support registry metadata fetching under bun package manager
	implement semaphore backpressure throttling in PackageManager

@​angular/build

Commit	Description
	implement semaphore backpressure throttling in JavaScriptTransformer

@​angular/ssr

... (truncated)

Changelog

Sourced from @​angular/build's changelog.

22.0.5 (2026-07-01)

@​angular/cli

Commit	Type	Description
f099e641c	fix	gracefully handle package manager errors in command handler
cf033ec48	fix	respect release age policy in update bootstrapping logic

@​schematics/angular

Commit	Type	Description
862a38069	fix	remove unused app tsconfig outDir

@​angular-devkit/build-angular

Commit	Type	Description
f75085f4b	fix	prevent OS command injection in ssr-dev-server builder

@​angular/build

Commit	Type	Description
dfee1e7b1	fix	auto-inject localize/init in library unit tests
aba718403	fix	inherit preserveSymlinks option from build target in unit-test builder
7c0d9f03c	fix	load zone.js dynamically for library unit tests
4288e4452	fix	scope createRequire module resolution using paths to prevent parent paths

@​angular/ssr

Commit	Type	Description
5f774f891	fix	preserve response headers during redirect

Commits

• 85a2698 release: cut the v22.0.5 release
• 5c892ee build: update cross-repo angular dependencies
• 7848e8d build: lock file maintenance
• 862a380 fix(@​schematics/angular): remove unused app tsconfig outDir
• 4288e44 fix(@​angular/build): scope createRequire module resolution using paths to pre...
• 5f774f8 fix(@​angular/ssr): preserve response headers during redirect
• 7c0d9f0 fix(@​angular/build): load zone.js dynamically for library unit tests
• f75085f fix(@​angular-devkit/build-angular): prevent OS command injection in ssr-dev-s...
• f099e64 fix(@​angular/cli): gracefully handle package manager errors in command handler
• cf033ec fix(@​angular/cli): respect release age policy in update bootstrapping logic
• Additional commits viewable in compare view

Updates ng-packagr from 21.2.5 to 22.0.1

Release notes

Sourced from ng-packagr's releases.

22.0.1

Bug Fixes

• ng-packagr: generate specific .npmignore entries for secondary entry-point package.json files (44bc3a7), closes #3343
• ng-packagr: prevent concurrent compilation and stale cache results (c4fd75f)

Performance

• ng-packagr: implement semaphore backpressure throttling in SassWorkerImplementation (1b6ac8e)

22.0.0

⚠ BREAKING CHANGES

• ng-packagr: TypeScript versions older than 6.0 are no longer supported.
• Node.js v20 is no longer supported. The minimum supported Node.js versions are now v22.22.0 and v24.13.1.

Features

• update @​angular/compiler-cli peer dependency to support Angular v22 (1fd8eb1)
• support Node.js 26 (4360fea)
• ng-packagr: drop support for TypeScript 5.9 (b59e280)

Bug Fixes

• ng-packagr: invalidate angularDiagnosticCache for html changes (e7d8e38)
• ng-packagr: handle package.json files with export subpaths (89e195d)
• ensure dts sourcemaps point to original ts files (28424e2)
• allow TypeScript 6 peer dependency (fdb49da)
• update minimum supported Node.js versions (f7e5ef5)

22.0.0-next.5

Bug Fixes

• ng-packagr: handle package.json files with export subpaths (89e195d)

22.0.0-next.4

Features

• support Node.js 26 (4360fea)

22.0.0-next.3

⚠ BREAKING CHANGES

• ng-packagr: TypeScript versions older than 6.0 are no longer supported.

Features

... (truncated)

Changelog

Sourced from ng-packagr's changelog.

22.0.1 (2026-07-01)

Bug Fixes

• ng-packagr: generate specific .npmignore entries for secondary entry-point package.json files (44bc3a7), closes #3343
• ng-packagr: prevent concurrent compilation and stale cache results (c4fd75f)

Performance

• ng-packagr: implement semaphore backpressure throttling in SassWorkerImplementation (1b6ac8e)

22.1.0-next.2 (2026-06-11)

Bug Fixes

• ng-packagr: prevent concurrent compilation and stale cache results (e5d77a7)

22.1.0-next.1 (2026-06-03)

22.1.0-next.0 (2026-06-03)

22.0.0 (2026-06-03)

⚠ BREAKING CHANGES

• ng-packagr: TypeScript versions older than 6.0 are no longer supported.
• Node.js v20 is no longer supported. The minimum supported Node.js versions are now v22.22.0 and v24.13.1.

Features

• update @​angular/compiler-cli peer dependency to support Angular v22 (1fd8eb1)
• support Node.js 26 (4360fea)
• ng-packagr: drop support for TypeScript 5.9 (b59e280)

Bug Fixes

• ng-packagr: invalidate angularDiagnosticCache for html changes (e7d8e38)
• ng-packagr: handle package.json files with export subpaths (89e195d)
• ensure dts sourcemaps point to original ts files (28424e2)
• allow TypeScript 6 peer dependency (fdb49da)
• update minimum supported Node.js versions (f7e5ef5)

22.0.0-rc.0 (2026-05-18)

22.0.0-next.5 (2026-05-18)

... (truncated)

Commits

• bb2a3af release: cut 22.0.1
• 44bc3a7 fix(ng-packagr): generate specific .npmignore entries for secondary entry-poi...
• 1b6ac8e perf(ng-packagr): implement semaphore backpressure throttling in SassWorkerIm...
• c4fd75f fix(ng-packagr): prevent concurrent compilation and stale cache results
• c2e12fb Update CHANGELOG.md
• dd927c6 docs: update changelog for version 22.0.0 release
• e918dc3 release: cut 22.0.0
• 7f8a814 build: update @​angular/compiler-cli peer dependency range to support version ...
• e7d8e38 fix(ng-packagr): invalidate angularDiagnosticCache for html changes
• 7204d85 build: update pnpm workspace configuration and remove redundant pnpm settings
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.