chore(deps): update dependency esbuild to v0.17.14

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
esbuild	0.17.4 -> 0.17.14

---

Release Notes

evanw/esbuild

v0.17.14

Compare Source

• Allow the TypeScript 5.0 const modifier in object type declarations (#​3021)

  The new TypeScript 5.0 const modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:

  interface Foo { <const T>(): T }
  type Bar = { new <const T>(): T }

• Implement preliminary lowering for CSS nesting (#​1945)

  Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!

  This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the :is() pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support :is() (e.g. Chrome 88+). You'll need to set esbuild's target to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a target which includes older browsers that don't support :is().

  The lowering transformation looks like this:

  /* Original input */
  a.btn {
    color: #​333;
    &:hover { color: #​444 }
    &:active { color: #​555 }
  }
  
  /* New output (with --target=chrome88) */
  a.btn {
    color: #​333;
  }
  a.btn:hover {
    color: #​444;
  }
  a.btn:active {
    color: #​555;
  }

  More complex cases may generate the :is() pseudo-class:

  /* Original input */
  div, p {
    .warning, .error {
      padding: 20px;
    }
  }
  
  /* New output (with --target=chrome88) */
  :is(div, p) :is(.warning, .error) {
    padding: 20px;
  }

  In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:

  ▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error]
  
      <stdin>:1:7:
        1 │ main { p { margin: auto } }
          │        ^
          ╵        :is(p)
  
    To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to
    prevent the rule from being parsed as a declaration.
  

  Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.

• Minification now removes unnecessary & CSS nesting selectors

  This release introduces the following CSS minification optimizations:

  /* Original input */
  a {
    font-weight: bold;
    & {
      color: blue;
    }
    & :hover {
      text-decoration: underline;
    }
  }
  
  /* Old output (with --minify) */
  a{font-weight:700;&{color:#​00f}& :hover{text-decoration:underline}}
  
  /* New output (with --minify) */
  a{font-weight:700;:hover{text-decoration:underline}color:#​00f}

• Minification now removes duplicates from CSS selector lists

  This release introduces the following CSS minification optimization:

  /* Original input */
  div, div { color: red }
  
  /* Old output (with --minify) */
  div,div{color:red}
  
  /* New output (with --minify) */
  div{color:red}

v0.17.13

Compare Source

• Work around an issue with NODE_PATH and Go's WebAssembly internals (#​3001)

  Go's WebAssembly implementation returns EINVAL instead of ENOTDIR when using the readdir syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering ENOTDIR causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy NODE_PATH feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting EINVAL into ENOTDIR for the readdir syscall.

• Fix a minification bug with CSS @layer rules that have parsing errors (#​3016)

  CSS at-rules require either a {} block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate @layer rules with parsing errors, and empty @layer rules cannot be removed because they have side effects (@layer didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard @layer rules with parsing errors when minifying (the rule @layer c has a parsing error):

  /* Original input */
  @​layer a {
    @​layer b {
      @​layer c
    }
  }
  
  /* Old output (with --minify) */
  @​layer a.b;
  
  /* New output (with --minify) */
  @​layer a.b.c;

• Unterminated strings in CSS are no longer an error

  The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:

  p {
    color: green;
    font-family: 'Courier New Times
    color: red;
    color: green;
  }

  ...would be treated the same as:

  p { color: green; color: green; }

  ...because the second declaration (from font-family to the semicolon after color: red) is invalid and is dropped.

  Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:

  /* esbuild's new non-minified output: */
  p {
    color: green;
    font-family: 'Courier New Times
    color: red;
    color: green;
  }

  /* esbuild's new minified output: */
  p{font-family:'Courier New Times
  color: red;color:green}

v0.17.12

Compare Source

• Fix a crash when parsing inline TypeScript decorators (#​2991)

  Previously esbuild's TypeScript parser crashed when parsing TypeScript decorators if the definition of the decorator was inlined into the decorator itself:

  @​(function sealed(constructor: Function) {
    Object.seal(constructor);
    Object.seal(constructor.prototype);
  })
  class Foo {}

  This crash was not noticed earlier because this edge case did not have test coverage. The crash is fixed in this release.

v0.17.11

Compare Source

• Fix the alias feature to always prefer the longest match (#​2963)

  It's possible to configure conflicting aliases such as --alias:a=b and --alias:a/c=d, which is ambiguous for the import path a/c/x (since it could map to either b/c/x or d/x). Previously esbuild would pick the first matching alias, which would non-deterministically pick between one of the possible matches. This release fixes esbuild to always deterministically pick the longest possible match.

• Minify calls to some global primitive constructors (#​2962)

  With this release, esbuild's minifier now replaces calls to Boolean/Number/String/BigInt with equivalent shorter code when relevant:

  // Original code
  console.log(
    Boolean(a ? (b | c) !== 0 : (c & d) !== 0),
    Number(e ? '1' : '2'),
    String(e ? '1' : '2'),
    BigInt(e ? 1n : 2n),
  )
  
  // Old output (with --minify)
  console.log(Boolean(a?(b|c)!==0:(c&d)!==0),Number(e?"1":"2"),String(e?"1":"2"),BigInt(e?1n:2n));
  
  // New output (with --minify)
  console.log(!!(a?b|c:c&d),+(e?"1":"2"),e?"1":"2",e?1n:2n);

• Adjust some feature compatibility tables for node (#​2940)

  This release makes the following adjustments to esbuild's internal feature compatibility tables for node, which tell esbuild which versions of node are known to support all aspects of that feature:

  • class-private-brand-checks: node v16.9+ => node v16.4+ (a decrease)
  • hashbang: node v12.0+ => node v12.5+ (an increase)
  • optional-chain: node v16.9+ => node v16.1+ (a decrease)
  • template-literal: node v4+ => node v10+ (an increase)

  Each of these adjustments was identified by comparing against data from the node-compat-table package and was manually verified using old node executables downloaded from https://nodejs.org/download/release/.

v0.17.10

Compare Source

• Update esbuild's handling of CSS nesting to match the latest specification changes (#​1945)

  The syntax for the upcoming CSS nesting feature has recently changed. The @nest prefix that was previously required in some cases is now gone, and nested rules no longer have to start with & (as long as they don't start with an identifier or function token).

  This release updates esbuild's pass-through handling of CSS nesting syntax to match the latest specification changes. So you can now use esbuild to bundle CSS containing nested rules and try them out in a browser that supports CSS nesting (which includes nightly builds of both Chrome and Safari).

  However, I'm not implementing lowering of nested CSS to non-nested CSS for older browsers yet. While the syntax has been decided, the semantics are still in flux. In particular, there is still some debate about changing the fundamental way that CSS nesting works. For example, you might think that the following CSS is equivalent to a .outer .inner button { ... } rule:

  .inner button {
    .outer & {
      color: red;
    }
  }

  But instead it's actually equivalent to a .outer :is(.inner button) { ... } rule which unintuitively also matches the following DOM structure:

  <div class="inner">
    <div class="outer">
      <button></button>
    </div>
  </div>

  The :is() behavior is preferred by browser implementers because it's more memory-efficient, but the straightforward translation into a .outer .inner button { ... } rule is preferred by developers used to the existing CSS preprocessing ecosystem (e.g. SASS). It seems premature to commit esbuild to specific semantics for this syntax at this time given the ongoing debate.

• Fix cross-file CSS rule deduplication involving url() tokens (#​2936)

  Previously cross-file CSS rule deduplication didn't handle url() tokens correctly. These tokens contain references to import paths which may be internal (i.e. in the bundle) or external (i.e. not in the bundle). When comparing two url() tokens for equality, the underlying import paths should be compared instead of their references. This release of esbuild fixes url() token comparisons. One side effect is that @font-face rules should now be deduplicated correctly across files:

  /* Original code */
  @​import "data:text/css, \
    @​import 'http://example.com/style.css'; \
    @​font-face { src: url(http://example.com/font.ttf) }";
  @​import "data:text/css, \
    @​font-face { src: url(http://example.com/font.ttf) }";
  
  /* Old output (with --bundle --minify) */
  @​import"http://example.com/style.css";@​font-face{src:url(http://example.com/font.ttf)}@​font-face{src:url(http://example.com/font.ttf)}
  
  /* New output (with --bundle --minify) */
  @​import"http://example.com/style.css";@​font-face{src:url(http://example.com/font.ttf)}

v0.17.9

Compare Source

• Parse rest bindings in TypeScript types (#​2937)

  Previously esbuild was unable to parse the following valid TypeScript code:

  let tuple: (...[e1, e2, ...es]: any) => any

  This release includes support for parsing code like this.

• Fix TypeScript code translation for certain computed declare class fields (#​2914)

  In TypeScript, the key of a computed declare class field should only be preserved if there are no decorators for that field. Previously esbuild always preserved the key, but esbuild will now remove the key to match the output of the TypeScript compiler:

  // Original code
  declare function dec(a: any, b: any): any
  declare const removeMe: unique symbol
  declare const keepMe: unique symbol
  class X {
      declare [removeMe]: any
      @​dec declare [keepMe]: any
  }
  
  // Old output
  var _a;
  class X {
  }
  removeMe, _a = keepMe;
  __decorateClass([
    dec
  ], X.prototype, _a, 2);
  
  // New output
  var _a;
  class X {
  }
  _a = keepMe;
  __decorateClass([
    dec
  ], X.prototype, _a, 2);

• Fix a crash with path resolution error generation (#​2913)

  In certain situations, a module containing an invalid import path could previously cause esbuild to crash when it attempts to generate a more helpful error message. This crash has been fixed.

v0.17.8

Compare Source

• Fix a minification bug with non-ASCII identifiers (#​2910)

  This release fixes a bug with esbuild where non-ASCII identifiers followed by a keyword were incorrectly not separated by a space. This bug affected both the in and instanceof keywords. Here's an example of the fix:

  // Original code
  π in a
  
  // Old output (with --minify --charset=utf8)
  πin a;
  
  // New output (with --minify --charset=utf8)
  π in a;

• Fix a regression with esbuild's WebAssembly API in version 0.17.6 (#​2911)

  Version 0.17.6 of esbuild updated the Go toolchain to version 1.20.0. This had the unfortunate side effect of increasing the amount of stack space that esbuild uses (presumably due to some changes to Go's WebAssembly implementation) which could cause esbuild's WebAssembly-based API to crash with a stack overflow in cases where it previously didn't crash. One such case is the package grapheme-splitter which contains code that looks like this:

  if (
    (0x0300 <= code && code <= 0x036F) ||
    (0x0483 <= code && code <= 0x0487) ||
    (0x0488 <= code && code <= 0x0489) ||
    (0x0591 <= code && code <= 0x05BD) ||
    // ... many hundreds of lines later ...
  ) {
    return;
  }

  This edge case involves a chain of binary operators that results in an AST over 400 nodes deep. Normally this wouldn't be a problem because Go has growable call stacks, so the call stack would just grow to be as large as needed. However, WebAssembly byte code deliberately doesn't expose the ability to manipulate the stack pointer, so Go's WebAssembly translation is forced to use the fixed-size WebAssembly call stack. So esbuild's WebAssembly implementation is vulnerable to stack overflow in cases like these.

  It's not unreasonable for this to cause a stack overflow, and for esbuild's answer to this problem to be "don't write code like this." That's how many other AST-manipulation tools handle this problem. However, it's possible to implement AST traversal using iteration instead of recursion to work around limited call stack space. This version of esbuild implements this code transformation for esbuild's JavaScript parser and printer, so esbuild's WebAssembly implementation is now able to process the grapheme-splitter package (at least when compiled with Go 1.20.0 and run with node's WebAssembly implementation).

v0.17.7

Compare Source

• Change esbuild's parsing of TypeScript instantiation expressions to match TypeScript 4.8+ (#​2907)

  This release updates esbuild's implementation of instantiation expression erasure to match microsoft/TypeScript#​49353. The new rules are as follows (copied from TypeScript's PR description):

  When a potential type argument list is followed by

  • a line break,
  • an ( token,
  • a template literal string, or
  • any token except < or > that isn't the start of an expression,

  we consider that construct to be a type argument list. Otherwise we consider the construct to be a < relational expression followed by a > relational expression.

• Ignore sideEffects: false for imported CSS files (#​1370, #​1458, #​2905)

  This release ignores the sideEffects annotation in package.json for CSS files that are imported into JS files using esbuild's css loader. This means that these CSS files are no longer be tree-shaken.

  Importing CSS into JS causes esbuild to automatically create a CSS entry point next to the JS entry point containing the bundled CSS. Previously packages that specified some form of "sideEffects": false could potentially cause esbuild to consider one or more of the JS files on the import path to the CSS file to be side-effect free, which would result in esbuild removing that CSS file from the bundle. This was problematic because the removal of that CSS is outwardly observable, since all CSS is global, so it was incorrect for previous versions of esbuild to tree-shake CSS files imported into JS files.

• Add constant folding for certain additional equality cases (#​2394, #​2895)

  This release adds constant folding for expressions similar to the following:

  // Original input
  console.log(
    null === 'foo',
    null === undefined,
    null == undefined,
    false === 0,
    false == 0,
    1 === true,
    1 == true,
  )
  
  // Old output
  console.log(
    null === "foo",
    null === void 0,
    null == void 0,
    false === 0,
    false == 0,
    1 === true,
    1 == true
  );
  
  // New output
  console.log(
    false,
    false,
    true,
    false,
    true,
    false,
    true
  );

v0.17.6

Compare Source

• Fix a CSS parser crash on invalid CSS (#​2892)

  Previously the following invalid CSS caused esbuild's parser to crash:

  @​media screen

  The crash was caused by trying to construct a helpful error message assuming that there was an opening { token, which is not the case here. This release fixes the crash.

• Inline TypeScript enums that are referenced before their declaration

  Previously esbuild inlined enums within a TypeScript file from top to bottom, which meant that references to TypeScript enum members were only inlined within the same file if they came after the enum declaration. With this release, esbuild will now inline enums even when they are referenced before they are declared:

  // Original input
  export const foo = () => Foo.FOO
  const enum Foo { FOO = 0 }
  
  // Old output (with --tree-shaking=true)
  export const foo = () => Foo.FOO;
  var Foo = /* @​__PURE__ */ ((Foo2) => {
    Foo2[Foo2["FOO"] = 0] = "FOO";
    return Foo2;
  })(Foo || {});
  
  // New output (with --tree-shaking=true)
  export const foo = () => 0 /* FOO */;

  This makes esbuild's TypeScript output smaller and faster when processing code that does this. I noticed this issue when I ran the TypeScript compiler's source code through esbuild's bundler. Now that the TypeScript compiler is going to be bundled with esbuild in the upcoming TypeScript 5.0 release, improvements like this will also improve the TypeScript compiler itself!

• Fix esbuild installation on Arch Linux (#​2785, #​2812, #​2865)

  Someone made an unofficial esbuild package for Linux that adds the ESBUILD_BINARY_PATH=/usr/bin/esbuild environment variable to the user's default environment. This breaks all npm installations of esbuild for users with this unofficial Linux package installed, which has affected many people. Most (all?) people who encounter this problem haven't even installed this unofficial package themselves; instead it was installed for them as a dependency of another Linux package. The problematic change to add the ESBUILD_BINARY_PATH environment variable was reverted in the latest version of this unofficial package. However, old versions of this unofficial package are still there and will be around forever. With this release, ESBUILD_BINARY_PATH is now ignored by esbuild's install script when it's set to the value /usr/bin/esbuild. This should unbreak using npm to install esbuild in these problematic Linux environments.

  Note: The ESBUILD_BINARY_PATH variable is an undocumented way to override the location of esbuild's binary when esbuild's npm package is installed, which is necessary to substitute your own locally-built esbuild binary when debugging esbuild's npm package. It's only meant for very custom situations and should absolutely not be forced on others by default, especially without their knowledge. I may remove the code in esbuild's installer that reads ESBUILD_BINARY_PATH in the future to prevent these kinds of issues. It will unfortunately make debugging esbuild harder. If ESBUILD_BINARY_PATH is ever removed, it will be done in a "breaking change" release.

v0.17.5

Compare Source

• Parse const type parameters from TypeScript 5.0

  The TypeScript 5.0 beta announcement adds const type parameters to the language. You can now add the const modifier on a type parameter of a function, method, or class like this:

  type HasNames = { names: readonly string[] };
  const getNamesExactly = <const T extends HasNames>(arg: T): T["names"] => arg.names;
  const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] });

  The type of names in the above example is readonly ["Alice", "Bob", "Eve"]. Marking the type parameter as const behaves as if you had written as const at every use instead. The above code is equivalent to the following TypeScript, which was the only option before TypeScript 5.0:

  type HasNames = { names: readonly string[] };
  const getNamesExactly = <T extends HasNames>(arg: T): T["names"] => arg.names;
  const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] } as const);

  You can read the announcement for more information.

• Make parsing generic async arrow functions more strict in .tsx files

  Previously esbuild's TypeScript parser incorrectly accepted the following code as valid:

  let fn = async <T> () => {};

  The official TypeScript parser rejects this code because it thinks it's the identifier async followed by a JSX element starting with <T>. So with this release, esbuild will now reject this syntax in .tsx files too. You'll now have to add a comma after the type parameter to get generic arrow functions like this to parse in .tsx files:

  let fn = async <T,> () => {};

• Allow the in and out type parameter modifiers on class expressions

  TypeScript 4.7 added the in and out modifiers on the type parameters of classes, interfaces, and type aliases. However, while TypeScript supported them on both class expressions and class statements, previously esbuild only supported them on class statements due to an oversight. This release now allows these modifiers on class expressions too:

  declare let Foo: any;
  Foo = class <in T> { };
  Foo = class <out T> { };

• Update enum constant folding for TypeScript 5.0

  TypeScript 5.0 contains an updated definition of what it considers a constant expression:

  An expression is considered a constant expression if it is

  • a number or string literal,
  • a unary +, -, or ~ applied to a numeric constant expression,
  • a binary +, -, *, /, %, **, <<, >>, >>>, |, &, ^ applied to two numeric constant expressions,
  • a binary + applied to two constant expressions whereof at least one is a string,
  • a template expression where each substitution expression is a constant expression,
  • a parenthesized constant expression,
  • a dotted name (e.g. x.y.z) that references a const variable with a constant expression initializer and no type annotation,
  • a dotted name that references an enum member with an enum literal type, or
  • a dotted name indexed by a string literal (e.g. x.y["z"]) that references an enum member with an enum literal type.

  This impacts esbuild's implementation of TypeScript's const enum feature. With this release, esbuild will now attempt to follow these new rules. For example, you can now initialize an enum member with a template literal expression that contains a numeric constant:

  // Original input
  const enum Example {
    COUNT = 100,
    ERROR = `Expected ${COUNT} items`,
  }
  console.log(
    Example.COUNT,
    Example.ERROR,
  )
  
  // Old output (with --tree-shaking=true)
  var Example = /* @​__PURE__ */ ((Example2) => {
    Example2[Example2["COUNT"] = 100] = "COUNT";
    Example2[Example2["ERROR"] = `Expected ${100 /* COUNT */} items`] = "ERROR";
    return Example2;
  })(Example || {});
  console.log(
    100 /* COUNT */,
    Example.ERROR
  );
  
  // New output (with --tree-shaking=true)
  console.log(
    100 /* COUNT */,
    "Expected 100 items" /* ERROR */
  );

  These rules are not followed exactly due to esbuild's limitations. The rule about dotted references to const variables is not followed both because esbuild's enum processing is done in an isolated module setting and because doing so would potentially require esbuild to use a type system, which it doesn't have. For example:

  // The TypeScript compiler inlines this but esbuild doesn't:
  declare const x = 'foo'
  const enum Foo { X = x }
  console.log(Foo.X)

  Also, the rule that requires converting numbers to a string currently only followed for 32-bit signed integers and non-finite numbers. This is done to avoid accidentally introducing a bug if esbuild's number-to-string operation doesn't exactly match the behavior of a real JavaScript VM. Currently esbuild's number-to-string constant folding is conservative for safety.

• Forbid definite assignment assertion operators on class methods

  In TypeScript, class methods can use the ? optional property operator but not the ! definite assignment assertion operator (while class fields can use both):

  class Foo {
    // These are valid TypeScript
    a?
    b!
    x?() {}
  
    // This is invalid TypeScript
    y!() {}
  }

  Previously esbuild incorrectly allowed the definite assignment assertion operator with class methods. This will no longer be allowed starting with this release.

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/Chicago, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
vite-plugin-docs	⬜️ Ignored (Inspect)			Mar 26, 2023 at 4:04AM (UTC)

[changeset-bot]

⚠️ No Changeset found

Latest commit: e1b611e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR