Bump esbuild from 0.14.54 to 0.17.19 #3

New Issue

fergalmoran · 2025-08-09T16:55:36Z

fergalmoran commented

2025-08-09 16:55:36 +00:00

Originally created by @dependabot[bot] on 5/15/2023

Bumps esbuild from 0.14.54 to 0.17.19.

Release notes

Sourced from esbuild's releases.

v0.17.19
Fix CSS transform bugs with nested selectors that start with a combinator (#3096)

This release fixes several bugs regarding transforming nested CSS into non-nested CSS for older browsers. The bugs were due to lack of test coverage for nested selectors with more than one compound selector where they all start with the same combinator. Here's what some problematic cases look like before and after these fixes:
/* Original code */
.foo {
  > &a,
  > &b {
    color: red;
  }
}
.bar {
  > &a,
  + &b {
    color: green;
  }
}
/* Old output (with --target=chrome90) */
.foo :is(> .fooa, > .foob) {
color: red;
}
.bar :is(> .bara, + .barb) {
color: green;
}
/* New output (with --target=chrome90) */
.foo > :is(a.foo, b.foo) {
color: red;
}
.bar > a.bar,
.bar + b.bar {
color: green;
}
Fix bug with TypeScript parsing of instantiation expressions followed by = (#3111)

This release fixes esbuild's TypeScript-to-JavaScript conversion code in the case where a potential instantiation expression is followed immediately by a = token (such that the trailing > becomes a >= token). Previously esbuild considered that to still be an instantiation expression, but the official TypeScript compiler considered it to be a >= operator instead. This release changes esbuild's interpretation to match TypeScript. This edge case currently appears to be problematic for other TypeScript-to-JavaScript converters as well:

Original code TypeScript esbuild 0.17.18 esbuild 0.17.19 Sucrase Babel

x<y>=a<b<c>>() x<y>=a(); x=a(); x<y>=a(); x=a() Invalid left-hand side in assignment expression

Avoid removing unrecognized directives from the directive prologue when minifying (#3115)

The directive prologue in JavaScript is a sequence of top-level string expressions that come before your code. The only directives that JavaScript engines currently recognize are use strict and sometimes use asm. However, the people behind React have made up their own directive for their own custom dialect of JavaScript. Previously esbuild only preserved the use strict directive when minifying, although you could still write React JavaScript with esbuild using something like --banner:js="'your directive here';". With this release, you can now put arbitrary directives in the entry point and esbuild will preserve them in its minified output:

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

d47ab43 publish 0.17.19 to npm
3a81eb5 update go 1.20.3 => 1.20.4
7cf5257 fix #3111: incorrect ts parsing of x \< y >= z
a3fcf70 fix #3096: css transform bug with nested selectors
c19689a fix #3115: pass through unknown js directives
d686756 minify: fold more shift operations when shorter
7d11ef1 fix for validation warnings
ee646b4 publish 0.17.18 to npm
ecea1f4 put back comment that was removed
9092a1b perf(linker): Fixes brute force chunk cycle detection (#3069)
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 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)

*Originally created by @dependabot[bot] on 5/15/2023* Bumps [esbuild](https://github.com/evanw/esbuild) from 0.14.54 to 0.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p> <blockquote> <h2>v0.17.19</h2> <ul> <li> <p>Fix CSS transform bugs with nested selectors that start with a combinator (<a href="https://redirect.github.com/evanw/esbuild/issues/3096">#3096</a>)</p> <p>This release fixes several bugs regarding transforming nested CSS into non-nested CSS for older browsers. The bugs were due to lack of test coverage for nested selectors with more than one compound selector where they all start with the same combinator. Here's what some problematic cases look like before and after these fixes:</p> <pre lang="css"><code>/* Original code */ .foo { > &a, > &b { color: red; } } .bar { > &a, + &b { color: green; } } <p>/* Old output (with --target=chrome90) */ .foo :is(> .fooa, > .foob) { color: red; } .bar :is(> .bara, + .barb) { color: green; }</p> <p>/* New output (with --target=chrome90) */ .foo > :is(a.foo, b.foo) { color: red; } .bar > a.bar, .bar + b.bar { color: green; } </code></pre></p> </li> <li> <p>Fix bug with TypeScript parsing of instantiation expressions followed by <code>=</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3111">#3111</a>)</p> <p>This release fixes esbuild's TypeScript-to-JavaScript conversion code in the case where a potential instantiation expression is followed immediately by a <code>=</code> token (such that the trailing <code>></code> becomes a <code>>=</code> token). Previously esbuild considered that to still be an instantiation expression, but the official TypeScript compiler considered it to be a <code>>=</code> operator instead. This release changes esbuild's interpretation to match TypeScript. This edge case currently <a href="https://sucrase.io/#transforms=typescript&compareWithTypeScript=true&code=x%3Cy%3E%3Da%3Cb%3Cc%3E%3E()">appears to be problematic</a> for other TypeScript-to-JavaScript converters as well:</p> <table> <thead> <tr> <th>Original code</th> <th>TypeScript</th> <th>esbuild 0.17.18</th> <th>esbuild 0.17.19</th> <th>Sucrase</th> <th>Babel</th> </tr> </thead> <tbody> <tr> <td><code>x<y>=a<b<c>>()</code></td> <td><code>x<y>=a();</code></td> <td><code>x=a();</code></td> <td><code>x<y>=a();</code></td> <td><code>x=a()</code></td> <td>Invalid left-hand side in assignment expression</td> </tr> </tbody> </table> </li> <li> <p>Avoid removing unrecognized directives from the directive prologue when minifying (<a href="https://redirect.github.com/evanw/esbuild/issues/3115">#3115</a>)</p> <p>The <a href="https://262.ecma-international.org/6.0/#sec-directive-prologues-and-the-use-strict-directive">directive prologue</a> in JavaScript is a sequence of top-level string expressions that come before your code. The only directives that JavaScript engines currently recognize are <code>use strict</code> and sometimes <code>use asm</code>. However, the people behind React have made up their own directive for their own custom dialect of JavaScript. Previously esbuild only preserved the <code>use strict</code> directive when minifying, although you could still write React JavaScript with esbuild using something like <code>--banner:js="'your directive here';"</code>. With this release, you can now put arbitrary directives in the entry point and esbuild will preserve them in its minified output:</p> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG-2022.md">esbuild's changelog</a>.</em></p> <blockquote> <h1>Changelog: 2022</h1> <p>This changelog documents all esbuild versions published in the year 2022 (versions 0.14.11 through 0.16.12).</p> <h2>0.16.12</h2> <ul> <li> <p>Loader defaults to <code>js</code> for extensionless files (<a href="https://redirect.github.com/evanw/esbuild/issues/2776">#2776</a>)</p> <p>Certain packages contain files without an extension. For example, the <code>yargs</code> package contains the file <code>yargs/yargs</code> which has no extension. Node, Webpack, and Parcel can all understand code that imports <code>yargs/yargs</code> 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 <code>""</code> (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:</p> <ul> <li> <p>CLI:</p> <pre><code>esbuild --bundle --loader:=css </code></pre> </li> <li> <p>JS:</p> <pre lang="js"><code>esbuild.build({ bundle: true, loader: { '': 'css' }, }) </code></pre> </li> <li> <p>Go:</p> <pre lang="go"><code>api.Build(api.BuildOptions{ Bundle: true, Loader: map[string]api.Loader{"": api.LoaderCSS}, }) </code></pre> </li> </ul> <p>In addition, the <code>"type"</code> field in <code>package.json</code> files now only applies to files with an explicit <code>.js</code>, <code>.jsx</code>, <code>.ts</code>, or <code>.tsx</code> extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than <code>.mjs</code>, <code>.mts</code>, <code>.cjs</code>, or <code>.cts</code> including extensionless files. So for example an extensionless file in a <code>"type": "module"</code> package is now treated as CommonJS instead of ESM.</p> </li> </ul> <h2>0.16.11</h2> <ul> <li> <p>Avoid a syntax error in the presence of direct <code>eval</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/2761">#2761</a>)</p> <p>The behavior of nested <code>function</code> declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested <code>function</code> 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 <code>function</code> declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:</p> <pre lang="js"><code>// Original code if (true) { function foo() {} console.log(!!foo) foo = null console.log(!!foo) } </code></pre> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/d47ab43980c457db27d2671ab618cd5c40a618a7"><code>d47ab43</code></a> publish 0.17.19 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/3a81eb5d03e2d33ef55555835e56ca8fc94e438e"><code>3a81eb5</code></a> update go 1.20.3 => 1.20.4</li> <li><a href="https://github.com/evanw/esbuild/commit/7cf5257e237c7629328cce29b98030a4b2b80472"><code>7cf5257</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3111">#3111</a>: incorrect ts parsing of <code>x \< y >= z</code></li> <li><a href="https://github.com/evanw/esbuild/commit/a3fcf7010e6677b26e645c459813fc05e123cda9"><code>a3fcf70</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3096">#3096</a>: css transform bug with nested selectors</li> <li><a href="https://github.com/evanw/esbuild/commit/c19689ab6eae9cbe7ecb742737fc7dc99bc7706d"><code>c19689a</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3115">#3115</a>: pass through unknown js directives</li> <li><a href="https://github.com/evanw/esbuild/commit/d68675666000999371fc2a45cccbcc0cff9f8bcf"><code>d686756</code></a> minify: fold more shift operations when shorter</li> <li><a href="https://github.com/evanw/esbuild/commit/7d11ef1e24a3f0981e45e37200957268c4e22619"><code>7d11ef1</code></a> fix for validation warnings</li> <li><a href="https://github.com/evanw/esbuild/commit/ee646b4ed8d3b9567e1a0ce2e478241b68a2a2e4"><code>ee646b4</code></a> publish 0.17.18 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/ecea1f4b9f812930a2dc104212e7f30eba679415"><code>ecea1f4</code></a> put back comment that was removed</li> <li><a href="https://github.com/evanw/esbuild/commit/9092a1ba1e7ccc92d0dfbb83eab3450cec279397"><code>9092a1b</code></a> perf(linker): Fixes brute force chunk cycle detection (<a href="https://redirect.github.com/evanw/esbuild/issues/3069">#3069</a>)</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.14.54...v0.17.19">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=esbuild&package-manager=npm_and_yarn&previous-version=0.14.54&new-version=0.17.19)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) </details>

fergalmoran added the dependencies dependencies dependencies labels 2025-08-09 16:55:37 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fergalmoran/dbg-otherway#3