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

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

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

• Fix TypeScript-specific class transform edge case (#3559)

  The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

  // Original code
  class Foo extends Bar {
    #private = 1;
    public: any;
    constructor() {
      super();
    }
  }
  // Old output (with esbuild v0.19.9)
  class Foo extends Bar {
  constructor() {
  super();
  this.#private = 1;
  }
  #private;
  }
  // Old output (with esbuild v0.19.10)
  class Foo extends Bar {
  constructor() {
  this.#private = 1;
  super();
  }
  #private;
  }
  // New output
  class Foo extends Bar {
  #private = 1;
  constructor() {
  super();
  }
  }

• Minifier: allow reording a primitive past a side-effect (#3568)

  The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (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

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for esbuild since your current version.

Updates @angular-devkit/build-angular from 15.2.10 to 21.2.19

Release notes

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

21.2.19

@​angular-devkit/build-angular

Commit	Description
	update http-proxy-middleware to 3.0.7

21.2.18

@​angular/cli

Commit	Description
	respect release age policy in update bootstrapping logic

@​angular/build

Commit	Description
	bump undici to 7.28.0
	bump vite to 7.3.6

21.2.17

@​angular/build

Commit	Description
	bump @​babel/core to 7.29.7
	bump esbuild to 0.28.1
	bump piscina to 5.2.0
	bump vite to 7.3.5

21.2.16

@​angular/cli

Commit	Description
	update pacote to 21.5.1

@​angular/ssr

Commit	Description
	prioritize options over environment variables in AngularNodeAppEngine

21.2.15

@​angular/cli

Commit	Description
	remove forceAuth and unscoped credential parsing
	support registry metadata fetching under bun package manager

21.2.14

@​angular/cli

Commit	Description
	expand package groups for newly added peer dependencies in update schematic

@​angular/build

| Commit | Description |

... (truncated)

Changelog

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

21.2.19 (2026-07-09)

@​angular-devkit/build-angular

Commit	Type	Description
df5429871	fix	update http-proxy-middleware to 3.0.7

20.3.32 (2026-07-09)

@​angular-devkit/build-angular

Commit	Type	Description
d4e07cb3e	fix	update http-proxy-middleware to 3.0.7

22.1.0-next.3 (2026-07-09)

@​angular/build

Commit	Type	Description
34d558c3c	feat	add built-in SQLite cache store fallback
52ae7f862	feat	share persistent build cache across git worktrees
41bd100dd	fix	fallback to build target preserveSymlinks option in karma runner
6d9b360e5	fix	prevent esbuild service hang on internal component stylesheet builds
85c53d990	fix	prevent externalizing builder-injected i18n locale data
004cc4104	fix	strip all vite id prefixes from minified code with external dependencies
09d0a11a8	perf	enable fast-path AST printing with sourcemaps in AotCompilation

@​angular/ssr

Commit	Type	Description
0bd22dae0	fix	replace all route parameters when resolving relative redirects

22.0.6 (2026-07-08)

... (truncated)

Commits

• 1a72825 release: cut the v21.2.19 release
• df54298 fix(@​angular-devkit/build-angular): update http-proxy-middleware to 3.0.7
• fe3a606 release: cut the v21.2.18 release
• 2510ee3 fix(@​angular/build): bump vite to 7.3.6
• 61a810a fix(@​angular/cli): respect release age policy in update bootstrapping logic
• a2b6116 fix(@​angular/build): bump undici to 7.28.0
• 9c1edbc release: cut the v21.2.17 release
• 637b848 fix(@​angular/build): bump piscina to 5.2.0
• 9c366e8 fix(@​angular/build): bump @​babel/core to 7.29.7
• 6a06ce9 fix(@​angular/build): bump esbuild to 0.28.1
• 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.

[semgrep-code-auth0-samples]

Semgrep found 1 ssc-ace67ff4-0843-40f4-a8d3-13e050943589 finding:

• angular8-ivy/package-lock.json
  • L12861 - Triage

Risk: Affected versions of js-yaml are vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). js-yaml is vulnerable to prototype pollution through its YAML merge key (<<) handling. When parsing untrusted YAML with load, loadAll, safeLoad, or safeLoadAll, a crafted document containing a __proto__ key inside a merged mapping can modify the prototype of the resulting object, leading to integrity violations in the application.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using js-yaml on the CLI

Fix: Upgrade this library to at least version 3.14.2 at angular2-jwt-samples/angular8-ivy/package-lock.json:12861.

Reference(s): GHSA-mh29-5h37-fv8m, CVE-2025-64718

Semgrep found 1 ssc-mal-11e0168e322a88b7a928c64b1f3ac77c0cab9fd6 finding:

• angular8-ivy/package-lock.json
  • L18703 - Triage

Risk: samples-bootstrap-theme contains malicious code. Remove it immediately.

Fix: There are no safe versions of this library available for upgrade. Library included at angular2-jwt-samples/angular8-ivy/package-lock.json:18703.

Reference(s): https://osv.dev/vulnerability/MAL-2022-5922

Semgrep found 1 ssc-b5be3fd7-c1fb-4156-b16f-2fc35cb62b00 finding:

• angular8-ivy/package-lock.json
  • L12861 - Triage

Risk: Affected versions of js-yaml are vulnerable to Inefficient Algorithmic Complexity / Uncontrolled Resource Consumption. An attacker can supply a YAML document containing a chain of mappings that each merge the previous one via the merge key (<<), causing js-yaml to spend quadratic CPU time while parsing input whose size grows only linearly, resulting in a denial of service.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using js-yaml on the CLI

Fix: Upgrade this library to at least version 3.15.0 at angular2-jwt-samples/angular8-ivy/package-lock.json:12861.

Reference(s): GHSA-52cp-r559-cp3m, CVE-2026-59869

Semgrep found 1 ssc-2427bad3-7619-448f-8f95-70806990606e finding:

• angular8-ivy/package-lock.json
  • L1649 - Triage

Risk: Affected versions of @angular/compiler are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). A stored XSS vulnerability in the Angular Template Compiler arises because its internal security schema doesn't classify certain URL‐ holding attributes (e.g. xlink:href, math|href, annotation|href) or the attributeName binding on SVG animation elements (<animate>, <set>, etc.) as requiring strict URL sanitization. An attacker who can supply untrusted input to template bindings like [attr.xlink:href] or <animate [attributeName]="'href'" [values]="maliciousURL"> can inject a javascript: URL payload. When the element is activated (e.g. clicked) or the animation runs, the malicious script executes in the application's origin, enabling session hijacking, data exfiltration, or unauthorized actions.

Manual Review Advice: A vulnerability from this advisory is reachable if you allow SVG/MathML attributes (e.g., xlink:href, href) or to the attributeName field of SVG animation tags (, , etc.) in HTML templates

Fix: Upgrade this library to at least version 19.2.17 at angular2-jwt-samples/angular8-ivy/package-lock.json:1649.

Reference(s): GHSA-v4hv-rgfq-gp49, CVE-2025-66412