Update dependency esbuild to v0.13.15 by rostomzed · Pull Request #73 · rostomzed/vscode

rostomzed · 2021-11-24T19:45:35Z

This PR contains the following updates:

Package	Type	Update	Change
esbuild	devDependencies	minor	`^0.11.12` -> `0.13.15`
esbuild	devDependencies	minor	`^0.12.6` -> `0.13.15`

Release Notes

evanw/esbuild

`v0.13.15`

Compare Source

Fix super in lowered async arrow functions (#1777)

This release fixes an edge case that was missed when lowering async arrow functions containing super property accesses for compile targets that don't support async such as with --target=es6. The problem was that lowering transforms async arrow functions into generator function expressions that are then passed to an esbuild helper function called __async that implements the async state machine behavior. Since function expressions do not capture this and super like arrow functions do, this led to a mismatch in behavior which meant that the transform was incorrect. The fix is to introduce a helper function to forward super access into the generator function expression body. Here's an example:
```
// Original code
class Foo extends Bar {
  foo() { return async () => super.bar() }
}

// Old output (with --target=es6)
class Foo extends Bar {
  foo() {
    return () => __async(this, null, function* () {
      return super.bar();
    });
  }
}

// New output (with --target=es6)
class Foo extends Bar {
  foo() {
    return () => {
      var __superGet = (key) => super[key];
      return __async(this, null, function* () {
        return __superGet("bar").call(this);
      });
    };
  }
}
```
Avoid merging certain CSS rules with different units (#1732)

This release no longer collapses border-radius, margin, padding, and inset rules when they have units with different levels of browser support. Collapsing multiple of these rules into a single rule is not equivalent if the browser supports one unit but not the other unit, since one rule would still have applied before the collapse but no longer applies after the collapse due to the whole rule being ignored. For example, Chrome 10 supports the rem unit but not the vw unit, so the CSS code below should render with rounded corners in Chrome 10. However, esbuild previously merged everything into a single rule which would cause Chrome 10 to ignore the rule and not round the corners. This issue is now fixed:
```
/* Original CSS */
div {
  border-radius: 1rem;
  border-top-left-radius: 1vw;
  margin: 0;
  margin-top: 1Q;
  left: 10Q;
  top: 20Q;
  right: 10Q;
  bottom: 20Q;
}

/* Old output (with --minify) */
div{border-radius:1vw 1rem 1rem;margin:1Q 0 0;inset:20Q 10Q}

/* New output (with --minify) */
div{border-radius:1rem;border-top-left-radius:1vw;margin:0;margin-top:1Q;inset:20Q 10Q}
```
Notice how esbuild can still collapse rules together when they all share the same unit, even if the unit is one that doesn't have universal browser support such as the unit Q. One subtlety is that esbuild now distinguishes between "safe" and "unsafe" units where safe units are old enough that they are guaranteed to work in any browser a user might reasonably use, such as px. Safe units are allowed to be collapsed together even if there are multiple different units while multiple different unsafe units are not allowed to be collapsed together. Another detail is that esbuild no longer minifies zero lengths by removing the unit if the unit is unsafe (e.g. 0rem into 0) since that could cause a rendering difference if a previously-ignored rule is now no longer ignored due to the unit change. If you are curious, you can learn more about browser support levels for different CSS units in Mozilla's documentation about CSS length units.
Avoid warning about ignored side-effect free imports for empty files (#1785)

When bundling, esbuild warns about bare imports such as import "lodash-es" when the package has been marked as "sideEffects": false in its package.json file. This is because the only reason to use a bare import is because you are relying on the side effects of the import, but imports for packages marked as side-effect free are supposed to be removed. If the package indicates that it has no side effects, then this bare import is likely a bug.

However, some people have packages just for TypeScript type definitions. These package can actually have a side effect as they can augment the type of the global object in TypeScript, even if they are marked with "sideEffects": false. To avoid warning in this case, esbuild will now only issue this warning if the imported file is non-empty. If the file is empty, then it's irrelevant whether you import it or not so any import of that file does not indicate a bug. This fixes this case because .d.ts files typically end up being empty after esbuild parses them since they typically only contain type declarations.
Attempt to fix packages broken due to the node: prefix (#1760)

Some people have started using the node-specific node: path prefix in their packages. This prefix forces the following path to be interpreted as a node built-in module instead of a package on the file system. So require("node:path") will always import node's path module and never import npm's path package.

Adding the node: prefix breaks that code with older node versions that don't understand the node: prefix. This is a problem with the package, not with esbuild. The package should be adding a fallback if the node: prefix isn't available. However, people still want to be able to use these packages with older node versions even though the code is broken. Now esbuild will automatically strip this prefix if it detects that the code will break in the configured target environment (as specified by --target=). Note that this only happens during bundling, since import paths are only examined during bundling.

`v0.13.14`

Compare Source

Fix dynamic import() on node 12.20+ (#1772)

When you use flags such as --target=node12.20, esbuild uses that version number to see what features the target environment supports. This consults an internal table that stores which target environments are supported for each feature. For example, import(x) is changed into Promise.resolve().then(() => require(x)) if dynamic import expressions are unsupported.

Previously esbuild's internal table only stored one version number, since features are rarely ever removed in newer versions of software. Either the target environment is before that version and the feature is unsupported, or the target environment is after that version and the feature is supported. This approach has work for all relevant features in all cases except for one: dynamic import support in node. This feature is supported in node 12.20.0 up to but not including node 13.0.0, and then is also supported in node 13.2.0 up. The feature table implementation has been changed to store an array of potentially discontiguous version ranges instead of one version number.

Up until now, esbuild used 13.2.0 as the lowest supported version number to avoid generating dynamic import expressions when targeting node versions that don't support it. But with this release, esbuild will now use the more accurate discontiguous version range in this case. This means dynamic import expressions can now be generated when targeting versions of node 12.20.0 up to but not including node 13.0.0.
Avoid merging certain qualified rules in CSS (#1776)

A change was introduced in the previous release to merge adjacent CSS rules that have the same content:
```
/* Original code */
a { color: red }
b { color: red }

/* Minified output */
a,b{color:red}
```
However, that introduced a regression in cases where the browser considers one selector to be valid and the other selector to be invalid, such as in the following example:
```
/* This rule is valid, and is applied */
a { color: red }

/* This rule is invalid, and is ignored */
b:-x-invalid { color: red }
```
Merging these two rules into one causes the browser to consider the entire merged rule to be invalid, which disables both rules. This is a change in behavior from the original code.

With this release, esbuild will now only merge adjacent duplicate rules together if they are known to work in all browsers (specifically, if they are known to work in IE 7 and up). Adjacent duplicate rules will no longer be merged in all other cases including modern pseudo-class selectors such as :focus, HTML5 elements such as video, and combinators such as a + b.
Minify syntax in the CSS font, font-family, and font-weight properties (#1756)

This release includes size reductions for CSS font syntax when minification is enabled:
```
/* Original code */
div {
  font: bold 1rem / 1.2 "Segoe UI", sans-serif, "Segoe UI Emoji";
}

/* Output with "--minify" */
div{font:700 1rem/1.2 Segoe UI,sans-serif,"Segoe UI Emoji"}
```
Notice how bold has been changed to 700 and the quotes were removed around "Segoe UI" since it was safe to do so.

This feature was contributed by @sapphi-red.

`v0.13.13`

Compare Source

Add more information about skipping "main" in package.json (#1754)

Configuring mainFields: [] breaks most npm packages since it tells esbuild to ignore the "main" field in package.json, which most npm packages use to specify their entry point. This is not a bug with esbuild because esbuild is just doing what it was told to do. However, people may do this without understanding how npm packages work, and then be confused about why it doesn't work. This release now includes additional information in the error message:
```
 > foo.js:1:27: error: Could not resolve "events" (use "--platform=node" when building for node)
     1 │ var EventEmitter = require('events')
       ╵                            ~~~~~~~~
   node_modules/events/package.json:20:2: note: The "main" field was ignored because the list of main fields to use is currently set to []
    20 │   "main": "./events.js",
       ╵   ~~~~~~
```
Fix a tree-shaking bug with var exports (#1739)

This release fixes a bug where a variable named var exports = {} was incorrectly removed by tree-shaking (i.e. dead code elimination). The exports variable is a special variable in CommonJS modules that is automatically provided by the CommonJS runtime. CommonJS modules are transformed into something like this before being run:
```
function(exports, module, require) {
  var exports = {}
}
```
So using var exports = {} should have the same effect as exports = {} because the variable exports should already be defined. However, esbuild was incorrectly overwriting the definition of the exports variable with the one provided by CommonJS. This release merges the definitions together so both are included, which fixes the bug.

Merge adjacent CSS selector rules with duplicate content (#1755)

With this release, esbuild will now merge adjacent selectors when minifying if they have the same content:

/* Original code */
a { color: red }
b { color: red }

/* Old output (with --minify) */
a{color:red}b{color:red}

/* New output (with --minify) */
a,b{color:red}

Shorten top, right, bottom, left CSS property into inset when it is supported (#1758)

This release enables collapsing of inset related properties:
```
/* Original code */
div {
  top: 0;
  right: 0;
  bottom: 0;
  left: 0;
}

/* Output with "--minify-syntax" */
div {
  inset: 0;
}
```
This minification rule is only enabled when inset property is supported by the target environment. Make sure to set esbuild's target setting correctly when minifying if the code will be running in an older environment (e.g. earlier than Chrome 87).

This feature was contributed by @sapphi-red.

`v0.13.12`

Compare Source

Implement initial support for simplifying calc() expressions in CSS (#1607)

This release includes basic simplification of calc() expressions in CSS when minification is enabled. The approach mainly follows the official CSS specification, which means it should behave the way browsers behave: https://www.w3.org/TR/css-values-4/#calc-func. This is a basic implementation so there are probably some calc() expressions that can be reduced by other tools but not by esbuild. This release mainly focuses on setting up the parsing infrastructure for calc() expressions to make it straightforward to implement additional simplifications in the future. Here's an example of this new functionality:
```
/* Input CSS */
div {
  width: calc(60px * 4 - 5px * 2);
  height: calc(100% / 4);
}

/* Output CSS (with --minify-syntax) */
div {
  width: 230px;
  height: 25%;
}
```
Expressions that can't be fully simplified will still be partially simplified into a reduced calc() expression:
```
/* Input CSS */
div {
  width: calc(100% / 5 - 2 * 1em - 2 * 1px);
}

/* Output CSS (with --minify-syntax) */
div {
  width: calc(20% - 2em - 2px);
}
```
Note that this transformation doesn't attempt to modify any expression containing a var() CSS variable reference. These variable references can contain any number of tokens so it's not safe to move forward with a simplification assuming that var() is a single token. For example, calc(2px * var(--x) * 3) is not transformed into calc(6px * var(--x)) in case var(--x) contains something like 4 + 5px (calc(2px * 4 + 5px * 3) evaluates to 23px while calc(6px * 4 + 5px) evaluates to 29px).
Fix a crash with a legal comment followed by an import (#1730)

Version 0.13.10 introduced parsing for CSS legal comments but caused a regression in the code that checks whether there are any rules that come before @import. This is not desired because browsers ignore @import rules after other non-@import rules, so esbuild warns you when you do this. However, legal comments are modeled as rules in esbuild's internal AST even though they aren't actual CSS rules, and the code that performs this check wasn't updated. This release fixes the crash.

`v0.13.11`

Compare Source

Implement class static blocks (#1558)

This release adds support for a new upcoming JavaScript feature called class static blocks that lets you evaluate code inside of a class body. It looks like this:
```
class Foo {
  static {
    this.foo = 123
  }
}
```
This can be useful when you want to use try/catch or access private #name fields during class initialization. Doing that without this feature is quite hacky and basically involves creating temporary static fields containing immediately-invoked functions and then deleting the fields after class initialization. Static blocks are much more ergonomic and avoid performance loss due to delete changing the object shape.

Static blocks are transformed for older browsers by moving the static block outside of the class body and into an immediately invoked arrow function after the class definition:
```
// The transformed version of the example code above
const _Foo = class {
};
let Foo = _Foo;
(() => {
  _Foo.foo = 123;
})();
```
In case you're wondering, the additional let variable is to guard against the potential reassignment of Foo during evaluation such as what happens below. The value of this must be bound to the original class, not to the current value of Foo:
```
let bar
class Foo {
  static {
    bar = () => this
  }
}
Foo = null
console.log(bar()) // This should not be "null"
```

Fix issues with super property accesses

Code containing super property accesses may need to be transformed even when they are supported. For example, in ES6 async methods are unsupported while super properties are supported. An async method containing super property accesses requires those uses of super to be transformed (the async function is transformed into a nested generator function and the super keyword cannot be used inside nested functions).

Previously esbuild transformed super property accesses into a function call that returned the corresponding property. However, this was incorrect for uses of super that write to the inherited setter since a function call is not a valid assignment target. This release fixes writing to a super property:

// Original code
class Base {
  set foo(x) { console.log('set foo to', x) }
}
class Derived extends Base {
  async bar() { super.foo = 123 }
}
new Derived().bar()

// Old output with --target=es6 (contains a syntax error)
class Base {
  set foo(x) {
    console.log("set foo to", x);
  }
}
class Derived extends Base {
  bar() {
    var __super = (key) => super[key];
    return __async(this, null, function* () {
      __super("foo") = 123;
    });
  }
}
new Derived().bar();

// New output with --target=es6 (works correctly)
class Base {
  set foo(x) {
    console.log("set foo to", x);
  }
}
class Derived extends Base {
  bar() {
    var __superSet = (key, value) => super[key] = value;
    return __async(this, null, function* () {
      __superSet("foo", 123);
    });
  }
}
new Derived().bar();

All known edge cases for assignment to a super property should now be covered including destructuring assignment and using the unary assignment operators with BigInts.

In addition, this release also fixes a bug where a static class field containing a super property access was not transformed when it was moved outside of the class body, which can happen when static class fields aren't supported.

// Original code
class Base {
  static get foo() {
    return 123
  }
}
class Derived extends Base {
  static bar = super.foo
}

// Old output with --target=es6 (contains a syntax error)
class Base {
  static get foo() {
    return 123;
  }
}
class Derived extends Base {
}
__publicField(Derived, "bar", super.foo);

// New output with --target=es6 (works correctly)
class Base {
  static get foo() {
    return 123;
  }
}
const _Derived = class extends Base {
};
let Derived = _Derived;
__publicField(Derived, "bar", __superStaticGet(_Derived, "foo"));

All known edge cases for super inside static class fields should be handled including accessing super after prototype reassignment of the enclosing class object.

`v0.13.10`

Compare Source

Implement legal comment preservation for CSS (#1539)

This release adds support for legal comments in CSS the same way they are already supported for JS. A legal comment is one that starts with /*! or that contains the text @license or @preserve. These comments are preserved in output files by esbuild since that follows the intent of the original authors of the code. The specific behavior is controlled via --legal-comments= in the CLI and legalComments in the JS API, which can be set to any of the following options:
- none: Do not preserve any legal comments
- inline: Preserve all rule-level legal comments
- eof: Move all rule-level legal comments to the end of the file
- linked: Move all rule-level legal comments to a .LEGAL.txt file and link to them with a comment
- external: Move all rule-level legal comments to a .LEGAL.txt file but to not link to them
The default behavior is eof when bundling and inline otherwise.
Allow uppercase es* targets (#1717)

With this release, you can now use target names such as ESNext instead of esnext as the target name in the CLI and JS API. This is important because people don't want to have to call .toLowerCase() on target strings from TypeScript's tsconfig.json file before passing it to esbuild (TypeScript uses case-agnostic target names).

This feature was contributed by @timse.
Update to Unicode 14.0.0

The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 13.0.0 to the newly release Unicode version 14.0.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/Unicode14.0.0/#Summary for more information about the changes.

`v0.13.9`

Compare Source

Add support for imports in package.json (#1691)

This release adds basic support for the imports field in package.json. It behaves similarly to the exports field but only applies to import paths that start with #. The imports field provides a way for a package to remap its own internal imports for itself, while the exports field provides a way for a package to remap its external exports for other packages. This is useful because the imports field respects the currently-configured conditions which means that the import mapping can change at run-time. For example:
```
$ cat entry.mjs
import '#example'

$ cat package.json
{
  "imports": {
    "#example": {
      "foo": "./example.foo.mjs",
      "default": "./example.mjs"
    }
  }
}

$ cat example.foo.mjs
console.log('foo is enabled')

$ cat example.mjs
console.log('foo is disabled')

$ node entry.mjs
foo is disabled

$ node --conditions=foo entry.mjs
foo is enabled
```
Now that esbuild supports this feature too, import paths starting with # and any provided conditions will be respected when bundling:
```
$ esbuild --bundle entry.mjs | node
foo is disabled

$ esbuild --conditions=foo --bundle entry.mjs | node
foo is enabled
```
Fix using npm rebuild with the esbuild package (#1703)

Version 0.13.4 accidentally introduced a regression in the install script where running npm rebuild multiple times could fail after the second time. The install script creates a copy of the binary executable using link followed by rename. Using link creates a hard link which saves space on the file system, and rename is used for safety since it atomically replaces the destination.

However, the rename syscall has an edge case where it silently fails if the source and destination are both the same link. This meant that the install script would fail after being run twice in a row. With this release, the install script now deletes the source after calling rename in case it has silently failed, so this issue should now be fixed. It should now be safe to use npm rebuild with the esbuild package.
Fix invalid CSS minification of border-radius (#1702)

CSS minification does collapsing of border-radius related properties. For example:
```
/* Original CSS */
div {
  border-radius: 1px;
  border-top-left-radius: 5px;
}

/* Minified CSS */
div{border-radius:5px 1px 1px}
```
However, this only works for numeric tokens, not identifiers. For example:
```
/* Original CSS */
div {
  border-radius: 1px;
  border-top-left-radius: inherit;
}

/* Minified CSS */
div{border-radius:1px;border-top-left-radius:inherit}
```
Transforming this to div{border-radius:inherit 1px 1px}, as was done in previous releases of esbuild, is an invalid transformation and results in incorrect CSS. This release of esbuild fixes this CSS transformation bug.

`v0.13.8`

Compare Source

Fix super inside arrow function inside lowered async function (#1425)

When an async function is transformed into a regular function for target environments that don't support async such as --target=es6, references to super inside that function must be transformed too since the async-to-regular function transformation moves the function body into a nested function, so the super references are no longer syntactically valid. However, this transform didn't handle an edge case and super references inside of an arrow function were overlooked. This release fixes this bug:

// Original code
class Foo extends Bar {
  async foo() {
    return () => super.foo()
  }
}

// Old output (with --target=es6)
class Foo extends Bar {
  foo() {
    return __async(this, null, function* () {
      return () => super.foo();
    });
  }
}

// New output (with --target=es6)
class Foo extends Bar {
  foo() {
    var __super = (key) => super[key];
    return __async(this, null, function* () {
      return () => __super("foo").call(this);
    });
  }
}

Remove the implicit / after [dir] in entry names (#1661)

The "entry names" feature lets you customize the way output file names are generated. The [dir] and [name] placeholders are filled in with the directory name and file name of the corresponding entry point file, respectively.

Previously --entry-names=[dir]/[name] and --entry-names=[dir][name] behaved the same because the value used for [dir] always had an implicit trailing slash, since it represents a directory. However, some people want to be able to remove the file name with --entry-names=[dir] and the implicit trailing slash gets in the way.

With this release, you can now use the [dir] placeholder without an implicit trailing slash getting in the way. For example, the command esbuild foo/bar/index.js --outbase=. --outdir=out --entry-names=[dir] previously generated the file out/foo/bar/.js but will now generate the file out/foo/bar.js.

`v0.13.7`

Compare Source

Minify CSS alpha values correctly (#1682)

When esbuild uses the rgba() syntax for a color instead of the 8-character hex code (e.g. when target is set to Chrome 61 or earlier), the 0-to-255 integer alpha value must be printed as a floating-point fraction between 0 and 1. The fraction was only printed to three decimal places since that is the minimal number of decimal places required for all 256 different alpha values to be uniquely determined. However, using three decimal places does not necessarily result in the shortest result. For example, 128 / 255 is 0.5019607843137255 which is printed as ".502" using three decimal places, but ".5" is equivalent because round(0.5 * 255) == 128, so printing ".5" would be better. With this release, esbuild will always use the minimal numeric representation for the alpha value:
```
/* Original code */
a { color: #FF800080 }

/* Old output (with --minify --target=chrome61) */
a{color:rgba(255,128,0,.502)}

/* New output (with --minify --target=chrome61) */
a{color:rgba(255,128,0,.5)}
```
Match node's behavior for core module detection (#1680)

Node has a hard-coded list of core modules (e.g. fs) that, when required, short-circuit the module resolution algorithm and instead return the corresponding internal core module object. When you pass --platform=node to esbuild, esbuild also implements this short-circuiting behavior and doesn't try to bundle these import paths. This was implemented in esbuild using the existing external feature (e.g. essentially --external:fs). However, there is an edge case where esbuild's external feature behaved differently than node.

Modules specified via esbuild's external feature also cause all sub-paths to be excluded as well, so for example --external:foo excludes both foo and foo/bar from the bundle. However, node's core module check is only an exact equality check, so for example fs is a core module and bypasses the module resolution algorithm but fs/foo is not a core module and causes the module resolution algorithm to search the file system.

This behavior can be used to load a module on the file system with the same name as one of node's core modules. For example, require('fs/') will load the module fs from the file system instead of loading node's core fs module. With this release, esbuild will now match node's behavior in this edge case. This means the external modules that are automatically added by --platform=node now behave subtly differently than --external:, which allows code that relies on this behavior to be bundled correctly.
Fix WebAssembly builds on Go 1.17.2+ (#1684)

Go 1.17.2 introduces a change (specifically a fix for CVE-2021-38297) that causes Go's WebAssembly bootstrap script to throw an error when it's run in situations with many environment variables. One such situation is when the bootstrap script is run inside GitHub Actions. This change was introduced because the bootstrap script writes a copy of the environment variables into WebAssembly memory without any bounds checking, and writing more than 4096 bytes of data ends up writing past the end of the buffer and overwriting who-knows-what. So throwing an error in this situation is an improvement. However, this breaks esbuild which previously (at least seemingly) worked fine.

With this release, esbuild's WebAssembly bootstrap script that calls out to Go's WebAssembly bootstrap script will now delete all environment variables except for the ones that esbuild checks for, of which there are currently only four: NO_COLOR, NODE_PATH, npm_config_user_agent, and WT_SESSION. This should avoid a crash when esbuild is built using Go 1.17.2+ and should reduce the likelihood of memory corruption when esbuild is built using Go 1.17.1 or earlier. This release also updates the Go version that esbuild ships with to version 1.17.2. Note that this problem only affects the esbuild-wasm package. The esbuild package is not affected.

See also:
- https://github.com/golang/go/issues/48797
- https://github.com/golang/go/issues/49011

`v0.13.6`

Compare Source

Emit decorators for declare class fields (#1675)

In version 3.7, TypeScript introduced the declare keyword for class fields that avoids generating any code for that field:

// TypeScript input
class Foo {
  a: number
  declare b: number
}

// JavaScript output
class Foo {
  a;
}

However, it turns out that TypeScript still emits decorators for these omitted fields. With this release, esbuild will now do this too:

// TypeScript input
class Foo {
  @&#8203;decorator a: number;
  @&#8203;decorator declare b: number;
}

// Old JavaScript output
class Foo {
  a;
}
__decorateClass([
  decorator
], Foo.prototype, "a", 2);

// New JavaScript output
class Foo {
  a;
}
__decorateClass([
  decorator
], Foo.prototype, "a", 2);
__decorateClass([
  decorator
], Foo.prototype, "b", 2);

Experimental support for esbuild on NetBSD (#1624)

With this release, esbuild now has a published binary executable for NetBSD in the esbuild-netbsd-64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @gdt.

⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️
Disable the "esbuild was bundled" warning if ESBUILD_BINARY_PATH is provided (#1678)

The ESBUILD_BINARY_PATH environment variable allows you to substitute an alternate binary executable for esbuild's JavaScript API. This is useful in certain cases such as when debugging esbuild. The JavaScript API has some code that throws an error if it detects that it was bundled before being run, since bundling prevents esbuild from being able to find the path to its binary executable. However, that error is unnecessary if ESBUILD_BINARY_PATH is present because an alternate path has been provided. This release disables the warning when ESBUILD_BINARY_PATH is present so that esbuild can be used when bundled as long as you also manually specify ESBUILD_BINARY_PATH.

This change was contributed by @heypiotr.
Remove unused catch bindings when minifying (#1660)

With this release, esbuild will now remove unused catch bindings when minifying:
```
// Original code
try {
  throw 0;
} catch (e) {
}

// Old output (with --minify)
try{throw 0}catch(t){}

// New output (with --minify)
try{throw 0}catch{}
```
This takes advantage of the new optional catch binding syntax feature that was introduced in ES2019. This minification rule is only enabled when optional catch bindings are supported by the target environment. Specifically, it's not enabled when using --target=es2018 or older. Make sure to set esbuild's target setting correctly when minifying if the code will be running in an older JavaScript environment.

This change was contributed by @sapphi-red.

`v0.13.5`

Compare Source

Improve watch mode accuracy (#1113)

Watch mode is enabled by --watch and causes esbuild to become a long-running process that automatically rebuilds output files when input files are changed. It's implemented by recording all calls to esbuild's internal file system interface and then invalidating the build whenever these calls would return different values. For example, a call to esbuild's internal ReadFile() function is considered to be different if either the presence of the file has changed (e.g. the file didn't exist before but now exists) or the presence of the file stayed the same but the content of the file has changed.

Previously esbuild's watch mode operated at the ReadFile() and ReadDirectory() level. When esbuild checked whether a directory entry existed or not (e.g. whether a directory contains a node_modules subdirectory or a package.json file), it called ReadDirectory() which then caused the build to depend on that directory's set of entries. This meant the build would be invalidated even if a new unrelated entry was added or removed, since that still changes the set of entries. This is problematic when using esbuild in environments that constantly create and destroy temporary directory entries in your project directory. In that case, esbuild's watch mode would constantly rebuild as the directory was constantly considered to be dirty.

With this release, watch mode now operates at the ReadFile() and ReadDirectory().Get() level. So when esbuild checks whether a directory entry exists or not, the build should now only depend on the presence status for that one directory entry. This should avoid unnecessary rebuilds due to unrelated directory entries being added or removed. The log messages generated using --watch will now also mention the specific directory entry whose presence status was changed if a build is invalidated for this reason.

Note that this optimization does not apply to plugins using the watchDirs return value because those paths are only specified at the directory level and do not describe individual directory entries. You can use watchFiles or watchDirs on the individual entries inside the directory to get a similar effect instead.

Disallow certain uses of < in .mts and .cts files

The upcoming version 4.5 of TypeScript is introducing the .mts and .cts extensions that turn into the .mjs and .cjs extensions when compiled. However, unlike the existing .ts and .tsx extensions, expressions that start with < are disallowed when they would be ambiguous depending on whether they are parsed in .ts or .tsx mode. The ambiguity is caused by the overlap between the syntax for JSX elements and the old deprecated syntax for type casts:

Syntax	`.ts`	`.tsx`	`.mts`/`.cts`
`<x>y`	✅ Type cast	🚫 Syntax error	🚫 Syntax error
`<T>() => {}`	✅ Arrow function	🚫 Syntax error	🚫 Syntax error
`<x>y</x>`	🚫 Syntax error	✅ JSX element	🚫 Syntax error
`<T>() => {}</T>`	🚫 Syntax error	✅ JSX element	🚫 Syntax error
`<T extends>() => {}</T>`	🚫 Syntax error	✅ JSX element	🚫 Syntax error
`<T extends={0}>() => {}</T>`	🚫 Syntax error	✅ JSX element	🚫 Syntax error
`<T,>() => {}`	✅ Arrow function	✅ Arrow function	✅ Arrow function
`<T extends X>() => {}`	✅ Arrow function	✅ Arrow function	✅ Arrow function

This release of esbuild introduces a syntax error for these ambiguous syntax constructs in .mts and .cts files to match the new behavior of the TypeScript compiler.

Do not remove empty @keyframes rules (#1665)

CSS minification in esbuild automatically removes empty CSS rules, since they have no effect. However, empty @keyframes rules still trigger JavaScript animation events so it's incorrect to remove them. To demonstrate that empty @keyframes rules still have an effect, here is a bug report for Firefox where it was incorrectly not triggering JavaScript animation events for empty @keyframes rules: https://bugzilla.mozilla.org/show_bug.cgi?id=1004377.

With this release, empty @keyframes rules are now preserved during minification:
```
/* Original CSS */
@&#8203;keyframes foo {
  from {}
  to {}
}

/* Old output (with --minify) */

/* New output (with --minify) */
@&#8203;keyframes foo{}
```
This fix was contributed by @eelco.
Fix an incorrect duplicate label error (#1671)

When labeling a statement in JavaScript, the label must be unique within the enclosing statements since the label determines the jump target of any labeled break or continue statement:
```
// This code is valid
x: y: z: break x;

// This code is invalid
x: y: x: break x;
```
However, an enclosing label with the same name is allowed as long as it's located in a different function body. Since break and continue statements can't jump across function boundaries, the label is not ambiguous. This release fixes a bug where esbuild incorrectly treated this valid code as a syntax error:
```
// This code is valid, but was incorrectly considered a syntax error
x: (() => {
  x: break x;
})();
```
This fix was contributed by @nevkontakte.

`v0.13.4`

Compare Source

Fix permission issues with the install script (#1642)

The esbuild package contains a small JavaScript stub file that implements the CLI (command-line interface). Its only purpose is to spawn the binary esbuild executable as a child process and forward the command-line arguments to it.

The install script contains an optimization that replaces this small JavaScript stub with the actual binary executable at install time to avoid the overhead of unnecessarily creating a new node process. This optimization can't be done at package publish time because there is only one esbuild package but there are many supported platforms, so the binary executable for the current platform must live outside of the esbuild package.

However, the optimization was implemented with an unlink operation followed by a link operation. This means that if the first step fails, the package is left in a broken state since the JavaScript stub file is deleted but not yet replaced.

With this release, the optimization is now implemented with a link operation followed by a rename operation. This should always leave the package in a working state even if either step fails.
Add a fallback for npm install esbuild --no-optional (#1647)

The installation method for esbuild's platform-specific binary executable was recently changed in version 0.13.0. Before that version esbuild downloaded it in an install script, and after that version esbuild lets the package manager download it using the optionalDependencies feature in package.json. This change was made because downloading the binary executable in an install script never really fully worked. The reasons are complex but basically there are a variety of edge cases where people people want to install esbuild in environments that they have customized such that downloading esbuild isn't possible. Using optionalDependencies instead lets the package manager deal with it instead, which should work fine in all cases (either that or your package manager has a bug, but that's not esbuild's problem).

There is one case where this new installation method doesn't work: if you pass the --no-optional flag to npm to disable the optionalDependencies feature. If you do this, you prevent esbuild from being installed. This is not a problem with esbuild because you are manually enabling a flag to change npm's behavior such that esbuild doesn't install correctly. However, people still want to do this.

With this release, esbuild will now fall back to the old installation method if the new installation method fails. THIS MAY NOT WORK. The new optionalDependencies installation method is the only supported way to install esbuild with npm. The old downloading installation method was removed because it doesn't always work. The downloading method is only being provided to try to be helpful but it's not the supported installation method. If you pass --no-optional and the download fails due to some environment customization you did, the recommended fix is to just remove the --no-optional flag.
Support the new .mts and .cts TypeScript file extensions

The upcoming version 4.5 of TypeScript has two new file extensions: .mts and .cts. Files with these extensions can be imported using the .mjs and .cjs, respectively. So the statement import "./foo.mjs" in TypeScript can actually succeed even if the file ./foo.mjs doesn't exist on the file system as long as the file ./foo.mts does exist. The import path with the .mjs extension is automatically re-routed to the corresponding file with the .mts extension at type-checking time by the TypeScript compiler. See the TypeScript 4.5 beta announcement for details.

With this release, esbuild will also automatically rewrite .mjs to .mts and .cjs to .cts when resolving import paths to files on the file system. This should make it possible to bundle code written in this new style. In addition, the extensions .mts and .cts are now also considered valid TypeScript file extensions by default along with the .ts extension.
Fix invalid CSS minification of margin and padding (#1657)

CSS minification does collapsing of margin and padding related properties. For example:
```
/* Original CSS */
div {
  margin: auto;
  margin-top: 5px;
  margin-left: 5px;
}

/* Minified CSS */
div{margin:5px auto auto 5px}
```
However, while this works for the auto keyword, it doesn't work for other keywords. For example:
```
/* Original CSS */
div {
  margin: inherit;
  margin-top: 5px;
  margin-left: 5px;
}

/* Minified CSS */
div{margin:inherit;margin-top:5px;margin-left:5px}
```
Transforming this to div{margin:5px inherit inherit 5px}, as was done in previous releases of esbuild, is an invalid transformation and results in incorrect CSS. This release of esbuild fixes this CSS transformation bug.

`v0.13.3`

Compare Source

Support TypeScript type-only import/export specifiers (#1637)

This release adds support for a new TypeScript syntax feature in the upcoming version 4.5 of TypeScript. This feature lets you prefix individual imports and exports with the type keyword to indicate that they are types instead of values. This helps tools such as esbuild omit them from your source code, and is necessary because esbuild compiles files one-at-a-time and doesn't know at parse time which imports/exports are types and which are values. The new syntax looks like this:
```
// Input TypeScript code
import { type Foo } from 'foo'
export { type Bar }

// Output JavaScript code (requires "importsNotUsedAsValues": "preserve" in "tsconfig.json")
import {} from "foo";
export {};
```
See microsoft/TypeScript#45998 for full details. From what I understand this is a purely ergonomic improvement since this was already previously possible using a type-only import/export statements like this:
```
// Input TypeScript code
import type { Foo } from 'foo'
export type { Bar }
import 'foo'
export {}

// Output JavaScript code (requires "importsNotUsedAsValues": "preserve" in "tsconfig.json")
import "foo";
export {};
```
This feature was contributed by @g-plane.

`v0.13.2`

Compare Source

Fix export {} statements with --tree-shaking=true (#1628)

The new --tree-shaking=true option allows you to force-enable tree shaking in cases where it wasn't previously possible. One such case is when bundling is disabled and there is no output format configured, in which case esbuild just preserves the format of whatever format the input code is in. Enabling tree shaking in this context caused a bug where export {} statements were stripped. This release fixes the bug so export {} statements should now be preserved when you pass --tree-shaking=true. This bug only affected this new functionality and didn't affect existing scenarios.

`v0.13.1`

Compare Source

Fix super in lowered async arrow functions (#1777)

This release fixes an edge case that was missed when lowering async arrow functions containing super property accesses for compile targets that don't support async such as with --target=es6. The problem was that lowering transforms async arrow functions into generator function expressions that are then passed to an esbuild helper function called __async that implements the async state machine behavior. Since function expressions do not capture this and super like arrow functions do, this led to a mismatch in behavior which meant that the transform was incorrect. The fix is to introduce a helper function to forward super access into the generator function expression body. Here's an example:
```
// Original code
class Foo extends Bar {
  foo() { return async () => super.bar() }
}

// Old output (with --target=es6)
class Foo extends Bar {
  foo() {
    return () => __async(this, null, function* () {
      return super.bar();
    });
  }
}

// New output (with --target=es6)
class Foo extends Bar {
  foo() {
    return () => {
      var __superGet = (key) => super[key];
      return __async(this, null, function* () {
        return __superGet("bar").call(this);
      });
    };
  }
}
```
Avoid merging certain CSS rules with different units (#1732)

This release no longer collapses border-radius, margin, padding, and inset rules when they have units with different levels of browser support. Collapsing multiple of these rules into a single rule is not equivalent if the browser supports one unit but not the other unit, since one rule would still have applied before the collapse but no longer applies after the collapse due to the whole rule being ignored. For example, Chrome 10 supports the rem unit but not the vw unit, so the CSS code below should render with rounded corners in Chrome 10. However, esbuild previously merged everything into a single rule which would cause Chrome 10 to ignore the rule and not round the corners. This issue is now fixed:
```
/* Original CSS */
div {
  border-radius: 1rem;
  border-top-left-radius: 1vw;
  margin: 0;
  margin-top: 1Q;
  left: 10Q;
  top: 20Q;
  right: 10Q;
  bottom: 20Q;
}

/* Old output (with --minify) */
div{border-radius:1vw 1rem 1rem;margin:1Q 0 0;inset:20Q 10Q}

/* New output (with --minify) */
div{border-radius:1rem;border-top-left-radius:1vw;margin:0;margin-top:1Q;inset:20Q 10Q}
```
Notice how esbuild can still collapse rules together when they all share the same unit, even if the unit is one that doesn't have universal browser support such as the unit Q. One subtlety is that esbuild now distinguishes between "safe" and "unsafe" units where safe units are old enough that they are guaranteed to work in any browser a user might reasonably use, such as px. Safe units are allowed to be collapsed together even if there are multiple different units while multiple different unsafe units are not allowed to be collapsed together. Another detail is that esbuild no longer minifies zero lengths by removing the unit if the unit is unsafe (e.g. 0rem into 0) since that could cause a rendering difference if a previously-ignored rule is now no longer ignored due to the unit change. If you are curious, you can learn more about browser support levels for different CSS units in Mozilla's documentation about CSS length units.
Avoid warning about ignored side-effect free imports for empty files (#1785)

When bundling, esbuild warns about bare imports such as import "lodash-es" when the package has been marked as "sideEffects": false in its package.json file. This is because the only reason to use a bare import is because you are relying on the side effects of the import, but imports for packages marked as side-effect free are supposed to be removed. If the package indicates that it has no side effects, then this bare import is likely a bug.

However, some people have packages just for TypeScript type definitions. These package can actually have a side effect as they can augment the type of the global object in TypeScript, even if they are marked with "sideEffects": false. To avoid warning in this case, esbuild will now only issue this warning if the imported file is non-empty. If the file is empty, then it's irrelevant whether you import it or not so any import of that file does not indicate a bug. This fixes this case because .d.ts files typically end up being empty after esbuild parses them since they typically only contain type declarations.
Attempt to fix packages broken due to the node: prefix (#1760)

Some people have started using the node-specific node: path prefix in their packages. This prefix forces the following path to be interpreted as a node built-in module instead of a package on the file system. So require("node:path") will always import node's path module and never import npm's path package.

Adding the node: prefix breaks that code with older node versions that don't understand the node: prefix. This is a problem with the package, not with esbuild. The package should be adding a fallback if the node: prefix isn't available. However, people still want to be able to use these packages with older node versions even though the code is broken. Now esbuild will automatically strip this prefix if it detects that the code will break in the configured target environment (as specified by --target=). Note that this only happens during bundling, since import paths are only examined during bundling.

`v0.13.0`

Compare Source

This release contains backwards-incompatible changes. Since esbuild is before version 1.0.0, these changes have been released as a new minor version to reflect this (as recommended by npm). You should either be pinning the exact version of esbuild in your package.json file or be using a version range syntax that only accepts patch upgrades such as ~0.12.0. See the documentation about semver for more information.

Allow tree shaking to be force-enabled and force-disabled ([#1518

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Update dependency esbuild to v0.13.15

968f1f8

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency esbuild to v0.13.15#73

Update dependency esbuild to v0.13.15#73
rostomzed wants to merge 1 commit intomainfrom
renovate/esbuild-0.x

rostomzed commented Nov 24, 2021

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

rostomzed commented Nov 24, 2021

Release Notes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant