Sourced from esbuild's releases.
v0.19.5
Fix a regression in 0.19.0 regarding
pathsintsconfig.json(#3354)The fix in esbuild version 0.19.0 to process
tsconfig.jsonaliases before the--packages=externalsetting unintentionally broke an edge case in esbuild's handling of certaintsconfig.jsonaliases where there are multiple files with the same name in different directories. This release adjusts esbuild's behavior for this edge case so that it passes while still processing aliases before--packages=external. Please read the linked issue for more details.Fix a CSS
fontproperty minification bug (#3452)This release fixes a bug where esbuild's CSS minifier didn't insert a space between the font size and the font family in the
fontCSS shorthand property in the edge case where the original source code didn't already have a space and the leading string token was shortened to an identifier:/* Original code */ .foo { font: 16px"Menlo"; }/* Old output (with --minify) */ .foo{font:16pxMenlo}
/* New output (with --minify) */ .foo{font:16px Menlo}
Fix bundling CSS with asset names containing spaces (#3410)
Assets referenced via CSS
url()tokens may cause esbuild to generate invalid output when bundling if the file name contains spaces (e.g.url(image 2.png)). With this release, esbuild will now quote all bundled asset references inurl()tokens to avoid this problem. This only affects assets loaded using thefileandcopyloaders.Fix invalid CSS
url()tokens in@importrules (#3426)In the future, CSS
url()tokens may contain additional stuff after the URL. This is irrelevant today as no CSS specification does this. But esbuild previously had a bug where using these tokens in an@importrule resulted in malformed output. This bug has been fixed.Fix
browser+false+type: moduleinpackage.json(#3367)The
browserfield inpackage.jsonallows you to map a file tofalseto have it be treated as an empty file when bundling for the browser. However, ifpackage.jsoncontains"type": "module"then all.jsfiles will be considered ESM, not CommonJS. Importing a named import from an empty CommonJS file gives you undefined, but importing a named export from an empty ESM file is a build error. This release changes esbuild's interpretation of these files mapped tofalsein this situation from ESM to CommonJS to avoid generating build errors for named imports.Fix a bug in top-level await error reporting (#3400)
Using
require()on a file that contains top-level await is not allowed becauserequire()must return synchronously and top-level await makes that impossible. You will get a build error if you try to bundle code that does this with esbuild. This release fixes a bug in esbuild's error reporting code for complex cases of this situation involving multiple levels of imports to get to the module containing the top-level await.Update to Unicode 15.1.0
The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 15.0.0 to the newly-released Unicode version 15.1.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.1.0/#Summary for more information about the changes.
This upgrade was contributed by
@JLHwung.v0.19.4
Fix printing of JavaScript decorators in tricky cases (#3396)
This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:
// Original code import { constant } from './constants.js'
... (truncated)
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
jsfor extensionless files (#2776)Certain packages contain files without an extension. For example, the
yargspackage contains the fileyargs/yargswhich has no extension. Node, Webpack, and Parcel can all understand code that importsyargs/yargsbecause 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:=cssJS:
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 inpackage.jsonfiles now only applies to files with an explicit.js,.jsx,.ts, or.tsxextension. Previously it was incorrectly applied by esbuild to all files that had an extension other than.mjs,.mts,.cjs, or.ctsincluding 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
functiondeclarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nestedfunctiondeclarations 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 nestedfunctiondeclarations 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)
a7fcc43
publish 0.19.5 to npm5870809
fix #3367:
ignore ESM flag for disabled modulesd5f397f
fix #3354:
tsconfig.json regression with paths72b1e8b
resolver: move IsExternal into PathPairb0eddea
fix #3400:
bug in top-level await error reporting47fc80b
fix #3426:
improve invalid url() token parsingd6973b9
css: fix url token backtracking with leading space30a43ec
fix #3410:
quote asset references in url tokensa579bd8
fix #3452:
insert space in font when minifyingcd91337
update go 1.20.7 => 1.20.10