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: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

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

@​schematics/angular

Commit	Description
	add less as a devDependency when selected as the style preprocessor
	correctly detect modules using new file extension format

@​angular/build

Commit	Description
	do not consider internal Angular files as external imports

20.0.1

@​schematics/angular

Commit	Description
	only overwrite JSON file if actually changed
	remove karma config devkit package usages during application migration
	skip zone.js dependency for zoneless applications

@​angular/cli

Commit	Description
	improve Node.js version check and error messages

@​angular/build

Commit	Description
	also disable outputMode in vitest unit-tests
	resolve junit karma reporter output to workspace root

20.0.0

@​angular/cli

Commit	Description
	add Node.js 24 as supported version
	remove Node.js v18 support
	update min Node.js support to 20.19, 22.12, and 24.0
	update minimum supported Node.js 22 version to 22.11.0

@​schematics/angular

Commit	Description
	Add global error listeners to new app generation
	add migration to update moduleResolution to bundler
	add migrations for server rendering updates
	Add prompt for new apps to be zoneless
	add update migration to keep previous style guide generation behavior
	directly use @angular/build in new projects
	generate applications using TypeScript project references
	generate libraries using TypeScript project references
	remove --server-routing option
	use TypeScript module preserve option for new projects
	add @angular/ssr dependency only when provideServerRendering import has been updated

... (truncated)

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

20.0.2 (2025-06-11)

@​schematics/angular

Commit	Type	Description
bf64a0f2d	fix	add less as a devDependency when selected as the style preprocessor
cb258a3e1	fix	correctly detect modules using new file extension format

@​angular/build

Commit	Type	Description
424f1cbbf	fix	do not consider internal Angular files as external imports

19.2.15 (2025-06-11)

@​angular-devkit/build-angular

Commit	Type	Description
b120e1411	fix	update dependency webpack-dev-server to v5.2.2

• e89245d release: cut the v20.0.2 release
• bf64a0f fix(@​schematics/angular): add less as a devDependency when selected as the ...
• 424f1cb fix(@​angular/build): do not consider internal Angular files as external imports
• 631ac7e ci: use new pull-request-labeling action
• fa25385 build: fix perf workflows
• 1db861c build: improve globbing of jasmine test files
• cb258a3 fix(@​schematics/angular): correctly detect modules using new file extension f...
• 19dc7dd build: simplify unit test target names
• d513e58 build: simplify unit test target names
• 4e7e0b0 release: cut the v20.0.1 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.