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 axios@0.30.0 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)

Sourced from esbuild's changelog.

Changelog: 2021

This changelog documents all esbuild versions published in the year 2021 (versions 0.8.29 through 0.14.10).

0.14.10

• Enable tree shaking of classes with lowered static fields (#175)

  If the configured target environment doesn't support static class fields, they are converted into a call to esbuild's __publicField function instead. However, esbuild's tree-shaking pass treated this call as a side effect, which meant that all classes with static fields were ineligible for tree shaking. This release fixes the problem by explicitly ignoring calls to the __publicField function during tree shaking side-effect determination. Tree shaking is now enabled for these classes:

  // Original code
  class Foo { static foo = 'foo' }
  class Bar { static bar = 'bar' }
  new Bar()
  // Old output (with --tree-shaking=true --target=es6)
  
  class Foo {
  
  }
  
  __publicField(Foo, "foo", "foo");
  
  class Bar {
  
  }
  
  __publicField(Bar, "bar", "bar");
  
  new Bar();
  // New output (with --tree-shaking=true --target=es6)
  
  class Bar {
  
  }
  
  __publicField(Bar, "bar", "bar");
  
  new Bar();
  
  

• Treat --define:foo=undefined as an undefined literal instead of an identifier (#1407)

  References to the global variable undefined are automatically replaced with the literal value for undefined, which appears as void 0 when printed. This allows for additional optimizations such as collapsing undefined ?? bar into just bar. However, this substitution was not done for values specified via --define:. As a result, esbuild could potentially miss out on certain optimizations in these cases. With this release, it's now possible to use --define: to substitute something with an undefined literal:

  // Original code
  let win = typeof window !== 'undefined' ? window : {}
  // Old output (with --define:window=undefined --minify)
  
  let win=typeof undefined!="undefined"?undefined:{};
  // New output (with --define:window=undefined --minify)
  
  let win={};
  
  

• Add the --drop:debugger flag (#1809)

  Passing this flag causes all debugger; statements to be removed from the output. This is similar to the drop_debugger: true flag available in the popular UglifyJS and Terser JavaScript minifiers.

... (truncated)

• 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

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

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
	use an empty array as default value for vitest exclude
	use date/time based output path for vitest unit-test

@​angular/ssr

Commit	Description
	ensure loadChildren runs in correct injection context during route extraction

20.1.0-rc.0

@​angular-devkit/build-angular

Commit	Description
	remove unused @vitejs/plugin-basic-ssl dependency

@​angular/build

Commit	Description
	proxy karma request from / to /base

... (truncated)

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

20.1.1 (2025-07-16)

@​angular/build

Commit	Type	Description
541b33f8d	fix	emit a warning when outputHashing is set to all or bundles when HMR is enabled
558a0fe92	fix	normalize code coverage include paths to POSIX

20.1.0 (2025-07-09)

@​angular/cli

Commit	Type	Description
dc45c186e	feat	add initial MCP server implementation

@​schematics/angular

Commit	Type	Description
1c19e0dcd	feat	use signal in app component

@​angular-devkit/build-angular

Commit	Type	Description
49a09737d	feat	provide partial custom postcss configuration support

@​angular/build

Commit	Type	Description
1159cf081	feat	add code coverage reporters option for unit-test
8f305ef0b	feat	add dataurl, base64 loaders
adfeee0a4	fix	adjust coverage includes/excludes for unit-test vitest runner
c19cd2985	fix	coverage reporter option
8879716ca	fix	expose unit test and karma builder API
a415a4999	fix	improve default coverage reporter handling for vitest
e0de8680d	fix	inject zone.js/testing before karma builder execution
2672f6ec1	fix	json and json-summary as vitest coverage reporters
b67fdfd6b	fix	resolve "Controller is already closed" error in Karma
2784883ec	fix	support extra test setup files with unit-test vitest runner
f177f5508	fix	support injecting global styles into vitest unit-tests
130c65014	fix	use an empty array as default value for vitest exclude
917af12ae	fix	use date/time based output path for vitest unit-test

... (truncated)

• 15c0148 release: cut the v20.1.1 release
• 0925ebd refactor(@​schematics/angular): fix layout of pill button
• b7121e8 build: update dependency node to v22.17.1
• 3ccd1e8 refactor(@​angular/build): provide private factory API for internal compilatio...
• eb29941 refactor(@​angular/cli): add a documentation search tool to MCP server
• 1602181 refactor(@​angular/build): use the toPosixPath util to convert windows file
• 558a0fe fix(@​angular/build): normalize code coverage include paths to POSIX
• 541b33f fix(@​angular/build): emit a warning when outputHashing is set to all or `...
• e46cedb refactor: use executeWithCases instead of RXJS boillerplate
• ed09cef release: cut the v20.1.0 release
• Additional commits viewable in compare view

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.