Bump the npm_and_yarn group across 1 directory with 3 updates

[dependabot]

Bumps the npm_and_yarn group with 2 updates in the / directory: @angular/common and brace-expansion.

Updates @angular/common from 21.2.17 to 22.1.0

Release notes

Sourced from @​angular/common's releases.

22.1.0

common

Commit	Description
	skip transfer cache for uncacheable HTTP traffic (#69017)

compiler

Commit	Description
	Add an error for --global-foo cases (#68846)
	Disable '--global-' error outside of g3 (#68846)
	Namespace CSS variables to the app (#68846)
	Support css var namespacing in properties (#68846)
	permissive whitespace parsing in default never blocks
	support foreign components defined outside top-level scope
	support foreign components inside control flow blocks (#69674)
	do not emit tag name when control flow root is foreign component (#69674)

compiler-cli

Commit	Description
	allow passing uninvoked signals as foreign component props
	support import aliases in foreignImports (#68674)

core

Commit	Description
	add custom set option to linkedSignal
	Adds deep linking from Performance panel to DevTools
	account for namespaces in host binding sanitization (#69558)
	correct container anchor collection order to match DOM layout
	introduce disposal mechanism for Angular views in foreign @content
	introduce logical-only containers for foreign content
	sanitize host bindings on concrete hosts (#69558)
	set current tnode in foreign component instruction on reuse

forms

Commit	Description
	add utility to assert that value is a field tree

http

Commit	Description
	add options to allow caching of credentialed and non-cacheable HTTP requests
	enable xsrf for root-provided HttpClient
	match header values exactly when deleting
	preserve immutability of materialized clones
	skip transfer cache for fetch credentialed requests (#69017)
	deprecate jsonp support

language-service

Commit	Description
	compile non-exported classes if standalone (#68454)
	Typecheck templates which would require inline typecheck blocks (#68454)

... (truncated)

Changelog

Sourced from @​angular/common's changelog.

22.1.0 (2026-07-29)

Deprecations

http

• HttpClient.jsonp, HttpClientJsonpModule, and related JSONP classes/functions are deprecated. Use standard HTTP requests instead.

common

Commit	Type	Description
1ad6824d0d	fix	skip transfer cache for uncacheable HTTP traffic (#69017)

compiler

Commit	Type	Description
af5e4e1131	feat	Add an error for --global-foo cases (#68846)
d579ecaf73	feat	Disable '--global-' error outside of g3 (#68846)
f98547675c	feat	Namespace CSS variables to the app (#68846)
8c8b2f7783	feat	Support css var namespacing in properties (#68846)
292199aa4d	fix	permissive whitespace parsing in default never blocks
25c744c4d0	fix	support foreign components defined outside top-level scope
5bd00add07	fix	support foreign components inside control flow blocks (#69674)
2e442f7876	perf	do not emit tag name when control flow root is foreign component (#69674)

compiler-cli

Commit	Type	Description
aeb55c8bc1	fix	allow passing uninvoked signals as foreign component props
7c60a98b3c	fix	support import aliases in foreignImports (#68674)

core

Commit	Type	Description
124ba10ead	feat	add custom set option to linkedSignal
eab4847a8b	feat	Adds deep linking from Performance panel to DevTools
091456a214	fix	account for namespaces in host binding sanitization (#69558)
b3748e9fe4	fix	correct container anchor collection order to match DOM layout
11b206b919	fix	introduce disposal mechanism for Angular views in foreign @content
56607967db	fix	introduce logical-only containers for foreign content
23cf1a828b	fix	sanitize host bindings on concrete hosts (#69558)
0c07356c5c	fix	set current tnode in foreign component instruction on reuse

forms

Commit	Type	Description
bbbd357bd2	fix	add utility to assert that value is a field tree

http

Commit	Type	Description
e3630c23c5	feat	add options to allow caching of credentialed and non-cacheable HTTP requests
ec16a3d6c6	fix	enable xsrf for root-provided HttpClient
39e362eea5	fix	match header values exactly when deleting
be46ca8696	fix	preserve immutability of materialized clones
c0cbd46bd7	fix	skip transfer cache for fetch credentialed requests (#69017)
af04e266cc	refactor	deprecate jsonp support

language-service

| Commit | Type | Description |

... (truncated)

Commits

• 79a37f3 refactor(common): replaces the deprecated positional subscribe arguments wi...
• 6dcb534 refactor(common): remove duplicate helper function
• ec16a3d fix(http): enable xsrf for root-provided HttpClient
• 39e362e fix(http): match header values exactly when deleting
• be46ca8 fix(http): preserve immutability of materialized clones
• d14696e fix(common): preserve crossorigin on image preloads
• 3192dcc fix(http): prevent transfer cache key collisions
• 359fb50 fix(common): avoid prototype lookups in date format caches
• 6d043f8 fix(http): prevent interceptor signal reads from leaking into calling reactiv...
• c1829f6 docs(docs-infra): Add build-time validation for API and guide links using rou...
• Additional commits viewable in compare view

Updates brace-expansion from 1.1.15 to 1.1.18

Commits

• 758fcd6 1.1.18
• 27fbeed Merge commit from fork
• 5c57cc2 1.1.17
• d757f1d npm ignore .claude
• cb4b9e4 fix: backport GHSA-mh99-v99m-4gvg (#129)
• 447763a 1.1.16
• d74e630 fix: v1 backport for CVE-2026-13149 (#122)
• See full diff in compare view

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

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.