chore(deps): bump esbuild and @angular-devkit/build-angular

[dependabot]

Bumps esbuild to 0.28.1 and updates ancestor dependency @angular-devkit/build-angular. 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-devkit/build-angular from 22.0.6 to 22.0.8

Release notes

Sourced from @​angular-devkit/build-angular's releases.

22.0.8

@​angular/cli

Commit	Description
	batch Prettier invocations during migration formatting
	update MCP devserver tool names to conform to spec regex

@​angular/build

Commit	Description
	canonicalize drive letter casing for workspace root on Windows
	ensure import map integrity keys are valid URL-like specifiers
	favor istanbul coverage provider when browser testing is enabled
	preserve custom config options in runnerConfig for vitest
	remap metafile paths when workspace root is a symlink or junction
	skip semantic affected-file walk when type checking is disabled

22.0.7

@​angular/cli

Commit	Description
	copy packageManager field and yarn config for temp installs
	support resolving subproject dependencies in pnpm workspaces

Changelog

Sourced from @​angular-devkit/build-angular's changelog.

22.0.8 (2026-07-23)

@​angular/cli

Commit	Type	Description
41c356256	fix	batch Prettier invocations during migration formatting
bc87c85c3	fix	update MCP devserver tool names to conform to spec regex

@​angular/build

Commit	Type	Description
5724bf632	fix	canonicalize drive letter casing for workspace root on Windows
b8bdbaa1e	fix	ensure import map integrity keys are valid URL-like specifiers
212a7bb21	fix	favor istanbul coverage provider when browser testing is enabled
bc760b005	fix	preserve custom config options in runnerConfig for vitest
19cda7415	fix	remap metafile paths when workspace root is a symlink or junction
fdcc98c79	perf	skip semantic affected-file walk when type checking is disabled

22.1.0-next.4 (2026-07-15)

@​angular/cli

Commit	Type	Description
3789ceee1	fix	copy packageManager field and yarn config for temp installs
b0b3a47ae	fix	support resolving subproject dependencies in pnpm workspaces

@​schematics/angular

Commit	Type	Description
b345bb54d	fix	remove unused spec tsconfig outDir

@​angular/build

Commit	Type	Description
0c18dc0f6	feat	emit debug ids for stable subresource integrity hashes
291caab61	fix	prevent stripping nested sourceMappingURL comments

... (truncated)

Commits

• beac493 release: cut the v22.0.8 release
• 1bb2cc5 build: update devinfra digest to 8819f0b
• 83eede6 build: update all github actions
• 15b8616 build: update dependency aspect_rules_ts to v3.9.2
• bc87c85 fix(@​angular/cli): update MCP devserver tool names to conform to spec regex
• 212a7bb fix(@​angular/build): favor istanbul coverage provider when browser testing is...
• 0c69328 Revert "perf(@​angular/build): skip semantic affected-file walk when type chec...
• ecc7aba build: update cross-repo angular dependencies
• ce5e5d0 build: lock file maintenance
• fdcc98c perf(@​angular/build): skip semantic affected-file walk when type checking is ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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]

Looks like these dependencies are up-to-date now, so this is no longer needed.