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.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
	add type checking of host bindings to strict config
	application migration should migrate karma builder package
	avoid empty polyfill option for new zoneless application
	default component templates to not use .ng.html extension
	drop composite in tsconfig
	ensure app-shell schematic consistently uses withAppShell
	ensure module discovery checks for an NgModule decorator
	generate component templates with a .ng.html file extension
	generate components without a .component extension/type
	generate directives without a .directive extension/type
	generate guards with a dash type separator
	generate interceptors with a dash type separator
	generate modules with a dash type separator
	generate pipes with a dash type separator
	generate resolvers with a dash type separator
	generate services without a .service extension/type
	infer app component name and path in server schematic
	migrate provideServerRoutesConfig to provideServerRendering
	relative tsconfig paths in references
	remove empty scripts option value from new applications
	Remove experimental from zoneless
	remove explicit outputPath option value from generated applications
	remove explicit index option from new applications
	remove setting files tsconfig field with SSR/Server generation
	set explicit type in library schematic
	skip spec project reference for minimal ng new
	support using default browser option when not present
	use protected for class member

... (truncated)

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

20.0.0 (2025-05-28)

Breaking Changes

@​angular/cli

• Node.js v18 is no longer supported with Angular.

  Before updating a project to Angular v20, the Node.js version must be at least 20.11.1. For the full list of supported Node.js versions, see https://angular.dev/reference/versions.

• Node.js versions from 22.0 to 22.10 are no longer supported

@​schematics/angular

• --server-routing option has been removed from several schematics. Server routing will be used when using the application builder.

@​angular-devkit/schematics

• The NodePackageLinkTask has been removed without a replacement. Create a custom task if needed.

  Note: This does not affect application developers.

@​angular/build

• TypeScript versions less than 5.8 are no longer supported.

@​schematics/angular

Commit	Type	Description
e03f2b899	feat	Add global error listeners to new app generation
1e137ca84	feat	add migration to update moduleResolution to bundler
26fd4ea73	feat	add migrations for server rendering updates
5876577af	feat	Add prompt for new apps to be zoneless
fdc6291dd	feat	add update migration to keep previous style guide generation behavior
093c5a315	feat	directly use @angular/build in new projects
d6f594fe0	feat	generate applications using TypeScript project references
0ab1ddf63	feat	generate libraries using TypeScript project references
18e13e2ce	feat	remove --server-routing option
03180fe03	feat	use TypeScript module preserve option for new projects
86d241629	fix	add @angular/ssr dependency only when provideServerRendering import has been updated
9e6b9b537	fix	add type checking of host bindings to strict config
8654b3fea	fix	application migration should migrate karma builder package
c557a19ef	fix	avoid empty polyfill option for new zoneless application
90615a88b	fix	default component templates to not use .ng.html extension
672ae14cd	fix	drop composite in tsconfig
da6ef626f	fix	ensure app-shell schematic consistently uses withAppShell
f126f8d34	fix	ensure module discovery checks for an NgModule decorator

... (truncated)

• 510db3e release: cut the v20.0.0 release
• b3fa0a8 build: update framework and ng-packagr to 20.0.0
• 2353de5 release: cut the v20.0.0-rc.4 release
• 817d8f1 build: update esbuild to v0.25.5
• fbdbe61 build: preserve peerDependenciesMeta in snapshots
• 646fbe1 refactor(@​angular/cli): allow opt-in Node.js compile cache for Bazel
• a2d77d3 refactor(@​angular-devkit/architect): remove redundant internal job schema val...
• ec94eb9 build: correctly replace BUILD_SCM_HASH-PLACEHOLDER with `BUILD_SCM_ABBREV_...
• 25c26ff build: update rules_angular digest to 652e5b0
• a9928cf build: update dependency node to v22.16.0
• Additional commits viewable in compare view

Sourced from ng-packagr's releases.

20.0.0

⚠ BREAKING CHANGES

• Node.js versions from 22.0 to 22.10 are no longer supported
• Node.js v18 is no longer supported
• TypeScript versions less than 5.8 are no longer supported.

Features

• expand browser support to widely available Baseline (94f7fbe)
• add DTS bundles for entry-points (ca9d568), closes #139
• support Angular version 20 (cebe060)
• drop support for TypeScript older than 5.8 (a8255ce)
• support Sass package importers (f767d3c)

Bug Fixes

• correctly resolve SCSS resources from nested paths (f34a73d), closes #3006
• correctly update reference to bin (e73db8e), closes #3062
• update min Node.js support to 20.19, 22.12, and 24.0 (5a7eac4)
• ensure in package .browserslistrc is correctly resolved (14ed50d)
• prevent nested CSS in components (e2d9ef0)
• disable TypeScript composite option with Angular compiler (5dfbdba)
• disable emitting empty chunk warning (638c107)
• remove Node.js v18 support (69d9d9e)
• update minimum supported Node.js 22 version to 22.11.0 (a836a71)

Performance

• optimize node deletion using Set (a99785c)
• prevent redundant entry-point builds in watch mode (2f2668b), closes #2936

20.0.0-rc.2

Bug Fixes

• correctly update reference to bin (e73db8e), closes #3062

20.0.0-rc.1

Bug Fixes

• update min Node.js support to 20.19, 22.12, and 24.0 (5a7eac4)

20.0.0-next.8

Bug Fixes

• ensure in package .browserslistrc is correctly resolved (14ed50d)

... (truncated)

Sourced from ng-packagr's changelog.

20.0.0 (2025-05-28)

⚠ BREAKING CHANGES

• Node.js versions from 22.0 to 22.11 are no longer supported
• Node.js v18 is no longer supported
• TypeScript versions less than 5.8 are no longer supported.

Features

• expand browser support to widely available Baseline (94f7fbe)
• add DTS bundles for entry-points (ca9d568), closes #139
• support Angular version 20 (cebe060)
• drop support for TypeScript older than 5.8 (a8255ce)
• support Sass package importers (f767d3c)

Bug Fixes

• correctly resolve SCSS resources from nested paths (f34a73d), closes #3006
• correctly update reference to bin (e73db8e), closes #3062
• update min Node.js support to 20.19, 22.12, and 24.0 (5a7eac4)
• ensure in package .browserslistrc is correctly resolved (14ed50d)
• prevent nested CSS in components (e2d9ef0)
• disable TypeScript composite option with Angular compiler (5dfbdba)
• disable emitting empty chunk warning (638c107)
• remove Node.js v18 support (69d9d9e)
• update minimum supported Node.js 22 version to 22.11.0 (a836a71)

Performance

• optimize node deletion using Set (a99785c)
• prevent redundant entry-point builds in watch mode (2f2668b), closes #2936

20.0.0-rc.2 (2025-05-27)

Bug Fixes

• correctly update reference to bin (e73db8e), closes #3062

20.0.0-rc.1 (2025-05-21)

Bug Fixes

• update min Node.js support to 20.19, 22.12, and 24.0 (5a7eac4)

20.0.0-rc.0 (2025-04-30)

20.0.0-next.8 (2025-04-23)

... (truncated)

• bc9ef06 docs: update changelog
• c47c6af release: cut 20.0.0
• 46a4345 build: update all non-major dependencies to v8.33.0
• 322173c release: cut 20.0.0-rc.2
• 22a7ba1 build: update typescript-eslint monorepo to v8
• e9aa810 Update discover-packages.ts
• 0d0711c Update .eslintrc.json
• 4d11154 build: remove unused @types/chokidar dependency
• 916f585 build: remove unused @types/read-pkg-up dependency
• e73db8e fix: correctly update reference to bin
• 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.