build(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.3 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.16 to 22.0.3

Release notes

Sourced from @​angular/build's releases.

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

Commit	Description
	avoid caching non-SSG page lookups
	correct grammar in console warning for redirected location headers
	prioritize options over environment variables in AngularNodeAppEngine

22.0.1

@​schematics/angular

Commit	Description
	fix browserMode option mapping in refactor-jasmine-vitest
	safely comment out multiline statements in refactor-jasmine-vitest
	use null objects and callbacks in karma-to-vitest migration

@​angular/cli

Commit	Description
	do not sort migrations of the same version alphabetically
	fallback to local package.json for schematic detection on first run
	isolate temporary package installation from parent pnpm workspace
	remove forceAuth and unscoped credential parsing
	validate registry option is a valid URL in ng add
	optimize update schematic registry query counts by fetching package metadata lazily

@​angular/build

Commit	Description
	allow disabling Vitest isolation from builder
	exclude JSON imports from Vite dependency optimization
	prevent concurrent stylesheet bundling esbuild context leaks
	restrict application builder output paths to output directory

22.0.0

@​schematics/angular

| Commit | Description |

... (truncated)

Changelog

Sourced from @​angular/build's changelog.

22.0.3 (2026-06-18)

@​schematics/angular

Commit	Type	Description
0eddea898	fix	remove default workspace vscode mcp.json configuration

Commits

• b30b9d3 release: cut the v22.0.3 release
• bc97bb3 build: update dependency vite to v7.3.5
• 0eddea8 fix(@​schematics/angular): remove default workspace vscode mcp.json configuration
• 08f9959 refactor(@​angular/cli): promote experimental MCP tools to stable
• aab6c10 release: cut the v22.0.2 release
• 376e4dc build: update cross-repo angular dependencies
• d996a27 fix(@​angular/ssr): avoid caching non-SSG page lookups
• 5714bfc build: update pnpm to v10.34.3
• f26011a build: lock file maintenance
• 2879ed9 build: update bazel dependencies
• Additional commits viewable in compare view

Updates ng-packagr from 21.2.3 to 22.0.0

Release notes

Sourced from ng-packagr's releases.

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

• ng-packagr: drop support for TypeScript 5.9 (b59e280)

Bug Fixes

• ng-packagr: resolve imports with TS extensions in rollup (804c04b), closes #3281

22.0.0-next.2

Features

• update to TypeScript 6 (f841ddf)

... (truncated)

Changelog

Sourced from ng-packagr's changelog.

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)

Bug Fixes

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

22.0.0-next.4 (2026-05-07)

Features

• support Node.js 26 (4360fea)

Commits

• 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
• 2684271 build: lock file maintenance
• 15a0f56 build: update dependency node to v24
• 5827827 build: update @​angular/ng-dev digest to a450a24
• 3439543 build: update pnpm to v11.4.0
• efed766 build: update dessant/lock-threads digest to 89ae32b
• 27ae92e build: update all non-major dependencies to v8.60.0
• Additional commits viewable in compare view