Bump esbuild and @angular-devkit/build-angular

[dependabot]

Bumps esbuild to 0.25.5 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.

Updates esbuild from 0.15.5 to 0.25.5

Release notes

Sourced from esbuild's releases.

v0.25.5

• Fix a regression with browser in package.json (#4187)

  The fix to #4144 in version 0.25.3 introduced a regression that caused browser overrides specified in package.json to fail to override relative path names that end in a trailing slash. That behavior change affected the [email protected] package. This regression has been fixed, and now has test coverage.

• Add support for certain keywords as TypeScript tuple labels (#4192)

  Previously esbuild could incorrectly fail to parse certain keywords as TypeScript tuple labels that are parsed by the official TypeScript compiler if they were followed by a ? modifier. These labels included function, import, infer, new, readonly, and typeof. With this release, these keywords will now be parsed correctly. Here's an example of some affected code:

  type Foo = [
    value: any,
    readonly?: boolean, // This is now parsed correctly
  ]

• Add CSS prefixes for the stretch sizing value (#4184)

  This release adds support for prefixing CSS declarations such as div { width: stretch }. That CSS is now transformed into this depending on what the --target= setting includes:

  div {
    width: -webkit-fill-available;
    width: -moz-available;
    width: stretch;
  }

v0.25.4

• Add simple support for CORS to esbuild's development server (#4125)

  Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code from localhost where the esbuild development server is running.

  To enable this use case, esbuild is adding a feature to allow Cross-Origin Resource Sharing (a.k.a. CORS) for simple requests. Specifically, passing your origin to the new cors option will now set the Access-Control-Allow-Origin response header when the request has a matching Origin header. Note that this currently only works for requests that don't send a preflight OPTIONS request, as esbuild's development server doesn't currently support OPTIONS requests.

  Some examples:

  • CLI:

    esbuild --servedir=. --cors-origin=https://example.com
    

  • JS:

    const ctx = await esbuild.context({})
    await ctx.serve({
      servedir: '.',
      cors: {

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2022

This changelog documents all esbuild versions published in the year 2022 (versions 0.14.11 through 0.16.12).

0.16.12

• Loader defaults to js for extensionless files (#2776)

  Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

  • CLI:

    esbuild --bundle --loader:=css
    

  • JS:

    esbuild.build({
      bundle: true,
      loader: { '': 'css' },
    })

  • Go:

    api.Build(api.BuildOptions{
      Bundle: true,
      Loader: map[string]api.Loader{"": api.LoaderCSS},
    })

  In addition, the "type" field in package.json files now only applies to files with an explicit .js, .jsx, .ts, or .tsx extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than .mjs, .mts, .cjs, or .cts including extensionless files. So for example an extensionless file in a "type": "module" package is now treated as CommonJS instead of ESM.

0.16.11

• Avoid a syntax error in the presence of direct eval (#2761)

  The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

  // Original code
  if (true) {
    function foo() {}
    console.log(!!foo)
    foo = null
    console.log(!!foo)
  }

... (truncated)

Commits

• ea453bf publish 0.25.5 to npm
• 223ddc6 fix #4187: browser package.json regression
• b2c8251 fix #4192: typescript tuple label parser edge case
• 28cf2f3 fix #4184: css prefixes for stretch
• bee1b09 fix comment indents
• 9ddfe5f run make update-compat-table
• c339f34 fix a misplaced comment
• 218d29e publish 0.25.4 to npm
• e66cd0b dev server: simple support for CORS requests (#4171)
• 8bf3368 js api: validate some options as arrays of strings
• Additional commits viewable in compare view

Updates @angular-devkit/build-angular from 14.2.13 to 20.1.3

Release notes

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

20.1.3

@​angular/build

Commit	Description
	update vite to 7.0.6

20.1.2

@​angular/cli

Commit	Description
	define option is being included multiple times in the JSON help

@​angular-devkit/core

Commit	Description
	use crypto.randomUUID instead of Date.now for unique string in tmp file names

20.1.1

@​angular/build

Commit	Description
	emit a warning when outputHashing is set to all or bundles when HMR is enabled
	normalize code coverage include paths to POSIX

20.1.0

@​schematics/angular

Commit	Description
	use signal in app component

@​angular/cli

Commit	Description
	add initial MCP server implementation

@​angular-devkit/build-angular

Commit	Description
	provide partial custom postcss configuration support

@​angular/build

Commit	Description
	add code coverage reporters option for unit-test
	add dataurl, base64 loaders
	adjust coverage includes/excludes for unit-test vitest runner
	coverage reporter option
	expose unit test and karma builder API
	improve default coverage reporter handling for vitest
	inject zone.js/testing before karma builder execution
	json and json-summary as vitest coverage reporters
	resolve "Controller is already closed" error in Karma
	support extra test setup files with unit-test vitest runner
	support injecting global styles into vitest unit-tests

... (truncated)

Changelog

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

20.1.3 (2025-07-24)

@​angular/build

Commit	Type	Description
ea5cd0e81	fix	update vite to 7.0.6

20.2.0-next.1 (2025-07-23)

@​angular/cli

Commit	Type	Description
fefa7a46f	fix	define option is being included multiple times in the JSON help

@​angular-devkit/core

Commit	Type	Description
7595e1f88	fix	use crypto.randomUUID instead of Date.now for unique string in tmp file names

@​angular/build

Commit	Type	Description
fb06bb505	feat	add headless mode for vitest browser mode

20.1.2 (2025-07-23)

@​angular/cli

Commit	Type	Description
96785224f	fix	define option is being included multiple times in the JSON help

@​angular-devkit/core

Commit	Type	Description
0d0040bdf	fix	use crypto.randomUUID instead of Date.now for unique string in tmp file names

... (truncated)

Commits

• 18b44f6 release: cut the v20.1.3 release
• ea5cd0e fix(@​angular/build): update vite to 7.0.6
• 0568f38 release: cut the v20.1.2 release
• 14da042 refactor(@​angular/cli): move MCP list projects tool to separate file
• 731d1a6 refactor(@​angular/cli): include content for top result in MCP documentation s...
• ada3e20 refactor(@​angular/cli): improve description of MCP documentation search tool
• 9678522 fix(@​angular/cli): define option is being included multiple times in the JS...
• 0d0040b fix(@​angular-devkit/core): use crypto.randomUUID instead of Date.now for uniq...
• 0a2340b refactor(@​angular/cli): add a get best practices guide MCP tool
• 9dfdaf5 test: use valid theme for material schematic
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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.