Sourced fromesbuild's releases.

v0.25.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version ofesbuild in yourpackage.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.24.0 or~0.24.0. See npm's documentation aboutsemver for more information.

• Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

  This change addresses esbuild's first security vulnerability report. Previously esbuild set theAccess-Control-Allow-Origin header to* to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information inthe report.

  Starting with this release,CORS will now be disabled, and requests will now be denied if the host does not match the one provided to--serve=. The default host is0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both127.0.0.1 and192.168.0.1). If you want to customize anything about esbuild's development server, you canput a proxy in front of esbuild and modify the incoming and/or outgoing requests.

  In addition, theserve() API call has been changed to return an array ofhosts instead of a singlehost string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

  Thanks to@​sapphi-red for reporting this issue.

• Delete output files when a build fails in watch mode (#3643)

  It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

• Fix correctness issues with the CSS nesting transform (#3620,#3877,#3933,#3997,#4005,#4037,#4038)

  This release fixes the following problems:

  • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using:is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

    /* Original code */.parent {> .a,> .b1> .b2 {color: red;  }}/* Old output (with --supported:nesting=false) */.parent>:is(.a, .b1> .b2) {color: red;}/* New output (with --supported:nesting=false) */.parent> .a,.parent> .b1> .b2 {color: red;}

    Thanks to@​tim-we for working on a fix.

  • The& CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered&& to have the same specificity as&. With this release, this should now work correctly:

    /* Original code (color should be red) */

... (truncated)

Sourced fromesbuild'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 andimport.meta (#4010,#4012,#4013)

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

  This fix was contributed by@​sapphi-red.

0.24.1

• Allowes2024 as a target intsconfig.json (#4004)

  TypeScript recentlyaddedes2024 as a compilation target, so esbuild now supports this in thetarget field oftsconfig.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 inthe documentation.

  This fix was contributed by@​billyjanitsch.

• Allow automatic semicolon insertion afterget/set

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

  classFoo{get*x(){}set*y(){}}

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

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

  Thedefine andpure 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)

• e9174d6 publish 0.25.0 to npm
• c27dbeb fixhosts inplugin-tests.js
• 6794f60 fixhosts innode-unref-tests.js
• de85afd Merge commit from fork
• da1de1b fix#4065: bitwise operators can return bigints
• f4e9d19 switch case liveness:default is always last
• 7aa47c3 fix#4028: minify live/deadswitch cases better
• 22ecd30 minify: more constant folding for strict equality
• 4cdf03c fix#4053: reordering of.tsx innode_modules
• dc71977 fix#3692:0 now picks a random ephemeral port
• Additional commits viewable incompare 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 theSecurity Alerts page.