chore(deps): update dependency esbuild to ^0.19.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
esbuild	^0.18.0 -> ^0.19.0

---

Release Notes

evanw/esbuild (esbuild)

v0.19.0

Compare Source

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

• Handle import paths containing wildcards (#​56, #​700, #​875, #​976, #​2221, #​2515)

  This release introduces wildcards in import paths in two places:

  • Entry points

    You can now pass a string containing glob-style wildcards such as ./src/*.ts as an entry point and esbuild will search the file system for files that match the pattern. This can be used to easily pass esbuild all files with a certain extension on the command line in a cross-platform way. Previously you had to rely on the shell to perform glob expansion, but that is obviously shell-dependent and didn't work at all on Windows. Note that to use this feature on the command line you will have to quote the pattern so it's passed verbatim to esbuild without any expansion by the shell. Here's an example:

    esbuild --minify "./src/*.ts" --outdir=out

    Specifically the * character will match any character except for the / character, and the /**/ character sequence will match a path separator followed by zero or more path elements. Other wildcard operators found in glob patterns such as ? and [...] are not supported.

  • Run-time import paths

    Import paths that are evaluated at run-time can now be bundled in certain limited situations. The import path expression must be a form of string concatenation and must start with either ./ or ../. Each non-string expression in the string concatenation chain becomes a wildcard. The * wildcard is chosen unless the previous character is a /, in which case the /**/* character sequence is used. Some examples:

    // These two forms are equivalent
    const json1 = await import('./data/' + kind + '.json')
    const json2 = await import(`./data/${kind}.json`)

    This feature works with require(...) and import(...) because these can all accept run-time expressions. It does not work with import and export statements because these cannot accept run-time expressions. If you want to prevent esbuild from trying to bundle these imports, you should move the string concatenation expression outside of the require(...) or import(...). For example:

    // This will be bundled
    const json1 = await import('./data/' + kind + '.json')
    
    // This will not be bundled
    const path = './data/' + kind + '.json'
    const json2 = await import(path)

    Note that using this feature means esbuild will potentially do a lot of file system I/O to find all possible files that might match the pattern. This is by design, and is not a bug. If this is a concern, I recommend either avoiding the /**/ pattern (e.g. by not putting a / before a wildcard) or using this feature only in directory subtrees which do not have many files that don't match the pattern (e.g. making a subdirectory for your JSON files and explicitly including that subdirectory in the pattern).

• Path aliases in tsconfig.json no longer count as packages (#​2792, #​3003, #​3160, #​3238)

  Setting --packages=external tells esbuild to make all import paths external when they look like a package path. For example, an import of ./foo/bar is not a package path and won't be external while an import of foo/bar is a package path and will be external. However, the paths field in tsconfig.json allows you to create import paths that look like package paths but that do not resolve to packages. People do not want these paths to count as package paths. So with this release, the behavior of --packages=external has been changed to happen after the tsconfig.json path remapping step.

• Use the local-css loader for .module.css files by default (#​20)

  With this release the css loader is still used for .css files except that .module.css files now use the local-css loader. This is a common convention in the web development community. If you need .module.css files to use the css loader instead, then you can override this behavior with --loader:.module.css=css.

v0.18.20

Compare Source

• Support advanced CSS @import rules (#​953, #​3137)

  CSS @import statements have been extended to allow additional trailing tokens after the import path. These tokens sort of make the imported file behave as if it were wrapped in a @layer, @supports, and/or @media rule. Here are some examples:

  @​import url(foo.css);
  @​import url(foo.css) layer;
  @​import url(foo.css) layer(bar);
  @​import url(foo.css) layer(bar) supports(display: flex);
  @​import url(foo.css) layer(bar) supports(display: flex) print;
  @​import url(foo.css) layer(bar) print;
  @​import url(foo.css) supports(display: flex);
  @​import url(foo.css) supports(display: flex) print;
  @​import url(foo.css) print;

  You can read more about this advanced syntax here. With this release, esbuild will now bundle @import rules with these trailing tokens and will wrap the imported files in the corresponding rules. Note that this now means a given imported file can potentially appear in multiple places in the bundle. However, esbuild will still only load it once (e.g. on-load plugins will only run once per file, not once per import).

v0.18.19

Compare Source

• Implement composes from CSS modules (#​20)

  This release implements the composes annotation from the CSS modules specification. It provides a way for class selectors to reference other class selectors (assuming you are using the local-css loader). And with the from syntax, this can even work with local names across CSS files. For example:

  // app.js
  import { submit } from './style.css'
  const div = document.createElement('div')
  div.className = submit
  document.body.appendChild(div)

  /* style.css */
  .button {
    composes: pulse from "anim.css";
    display: inline-block;
  }
  .submit {
    composes: button;
    font-weight: bold;
  }

  /* anim.css */
  @​keyframes pulse {
    from, to { opacity: 1 }
    50% { opacity: 0.5 }
  }
  .pulse {
    animation: 2s ease-in-out infinite pulse;
  }

  Bundling this with esbuild using --bundle --outdir=dist --loader:.css=local-css now gives the following:

  (() => {
    // style.css
    var submit = "anim_pulse style_button style_submit";
  
    // app.js
    var div = document.createElement("div");
    div.className = submit;
    document.body.appendChild(div);
  })();

  /* anim.css */
  @​keyframes anim_pulse {
    from, to {
      opacity: 1;
    }
    50% {
      opacity: 0.5;
    }
  }
  .anim_pulse {
    animation: 2s ease-in-out infinite anim_pulse;
  }
  
  /* style.css */
  .style_button {
    display: inline-block;
  }
  .style_submit {
    font-weight: bold;
  }

  Import paths in the composes: ... from syntax are resolved using the new composes-from import kind, which can be intercepted by plugins during import path resolution when bundling is enabled.

  Note that the order in which composed CSS classes from separate files appear in the bundled output file is deliberately undefined by design (see the specification for details). You are not supposed to declare the same CSS property in two separate class selectors and then compose them together. You are only supposed to compose CSS class selectors that declare non-overlapping CSS properties.

  Issue #​20 (the issue tracking CSS modules) is esbuild's most-upvoted issue! With this change, I now consider esbuild's implementation of CSS modules to be complete. There are still improvements to make and there may also be bugs with the current implementation, but these can be tracked in separate issues.

• Fix non-determinism with tsconfig.json and symlinks (#​3284)

  This release fixes an issue that could cause esbuild to sometimes emit incorrect build output in cases where a file under the effect of tsconfig.json is inconsistently referenced through a symlink. It can happen when using npm link to create a symlink within node_modules to an unpublished package. The build result was non-deterministic because esbuild runs module resolution in parallel and the result of the tsconfig.json lookup depended on whether the import through the symlink or not through the symlink was resolved first. This problem was fixed by moving the realpath operation before the tsconfig.json lookup.

• Add a hash property to output files (#​3084, #​3293)

  As a convenience, every output file in esbuild's API now includes a hash property that is a hash of the contents field. This is the hash that's used internally by esbuild to detect changes between builds for esbuild's live-reload feature. You may also use it to detect changes between your own builds if its properties are sufficient for your use case.

  This feature has been added directly to output file objects since it's just a hash of the contents field, so it makes conceptual sense to store it in the same location. Another benefit of putting it there instead of including it as a part of the watch mode API is that it can be used without watch mode enabled. You can use it to compare the output of two independent builds that were done at different times.

  The hash algorithm (currently XXH64) is implementation-dependent and may be changed at any time in between esbuild versions. If you don't like esbuild's choice of hash algorithm then you are welcome to hash the contents yourself instead. As with any hash algorithm, note that while two different hashes mean that the contents are different, two equal hashes do not necessarily mean that the contents are equal. You may still want to compare the contents in addition to the hashes to detect with certainty when output files have been changed.

• Avoid generating duplicate prefixed declarations in CSS (#​3292)

  There was a request for esbuild's CSS prefixer to avoid generating a prefixed declaration if a declaration by that name is already present in the same rule block. So with this release, esbuild will now avoid doing this:

  /* Original code */
  body {
    backdrop-filter: blur(30px);
    -webkit-backdrop-filter: blur(45px);
  }
  
  /* Old output (with --target=safari12) */
  body {
    -webkit-backdrop-filter: blur(30px);
    backdrop-filter: blur(30px);
    -webkit-backdrop-filter: blur(45px);
  }
  
  /* New output (with --target=safari12) */
  body {
    backdrop-filter: blur(30px);
    -webkit-backdrop-filter: blur(45px);
  }

  This can result in a visual difference in certain cases (for example if the browser understands blur(30px) but not blur(45px), it will be able to fall back to blur(30px)). But this change means esbuild now matches the behavior of Autoprefixer which is probably a good representation of how people expect this feature to work.

v0.18.18

Compare Source

• Fix asset references with the --line-limit flag (#​3286)

  The recently-released --line-limit flag tells esbuild to terminate long lines after they pass this length limit. This includes automatically wrapping long strings across multiple lines using escaped newline syntax. However, using this could cause esbuild to generate incorrect code for references from generated output files to assets in the bundle (i.e. files loaded with the file or copy loaders). This is because esbuild implements asset references internally using find-and-replace with a randomly-generated string, but the find operation fails if the string is split by an escaped newline due to line wrapping. This release fixes the problem by not wrapping these strings. This issue affected asset references in both JS and CSS files.

• Support local names in CSS for @keyframe, @counter-style, and @container (#​20)

  This release extends support for local names in CSS files loaded with the local-css loader to cover the @keyframe, @counter-style, and @container rules (and also animation, list-style, and container declarations). Here's an example:

  @​keyframes pulse {
    from, to { opacity: 1 }
    50% { opacity: 0.5 }
  }
  @​counter-style moon {
    system: cyclic;
    symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔;
  }
  @​container squish {
    li { float: left }
  }
  ul {
    animation: 2s ease-in-out infinite pulse;
    list-style: inside moon;
    container: squish / size;
  }

  With the local-css loader enabled, that CSS will be turned into something like this (with the local name mapping exposed to JS):

  @​keyframes stdin_pulse {
    from, to {
      opacity: 1;
    }
    50% {
      opacity: 0.5;
    }
  }
  @​counter-style stdin_moon {
    system: cyclic;
    symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔;
  }
  @​container stdin_squish {
    li {
      float: left;
    }
  }
  ul {
    animation: 2s ease-in-out infinite stdin_pulse;
    list-style: inside stdin_moon;
    container: stdin_squish / size;
  }

  If you want to use a global name within a file loaded with the local-css loader, you can use a :global selector to do that:

  div {
    /* All symbols are global inside this scope (i.e.
     * "pulse", "moon", and "squish" are global below) */
    :global {
      animation: 2s ease-in-out infinite pulse;
      list-style: inside moon;
      container: squish / size;
    }
  }

  If you want to use @keyframes, @counter-style, or @container with a global name, make sure it's in a file that uses the css or global-css loader instead of the local-css loader. For example, you can configure --loader:.module.css=local-css so that the local-css loader only applies to *.module.css files.

• Support strings as keyframe animation names in CSS (#​2555)

  With this release, esbuild will now parse animation names that are specified as strings and will convert them to identifiers. The CSS specification allows animation names to be specified using either identifiers or strings but Chrome only understands identifiers, so esbuild will now always convert string names to identifier names for Chrome compatibility:

  /* Original code */
  @​keyframes "hide menu" {
    from { opacity: 1 }
    to { opacity: 0 }
  }
  menu.hide {
    animation: 0.5s ease-in-out "hide menu";
  }
  
  /* Old output */
  @​keyframes "hide menu" { from { opacity: 1 } to { opacity: 0 } }
  menu.hide {
    animation: 0.5s ease-in-out "hide menu";
  }
  
  /* New output */
  @​keyframes hide\ menu {
    from {
      opacity: 1;
    }
    to {
      opacity: 0;
    }
  }
  menu.hide {
    animation: 0.5s ease-in-out hide\ menu;
  }

v0.18.17

Compare Source

• Support An+B syntax and :nth-*() pseudo-classes in CSS

  This adds support for the :nth-child(), :nth-last-child(), :nth-of-type(), and :nth-last-of-type() pseudo-classes to esbuild, which has the following consequences:

  • The An+B syntax is now parsed, so parse errors are now reported
  • An+B values inside these pseudo-classes are now pretty-printed (e.g. a leading + will be stripped because it's not in the AST)
  • When minification is enabled, An+B values are reduced to equivalent but shorter forms (e.g. 2n+0 => 2n, 2n+1 => odd)
  • Local CSS names in an of clause are now detected (e.g. in :nth-child(2n of :local(.foo)) the name foo is now renamed)

  /* Original code */
  .foo:nth-child(+2n+1 of :local(.bar)) {
    color: red;
  }
  
  /* Old output (with --loader=local-css) */
  .stdin_foo:nth-child(+2n + 1 of :local(.bar)) {
    color: red;
  }
  
  /* New output (with --loader=local-css) */
  .stdin_foo:nth-child(2n+1 of .stdin_bar) {
    color: red;
  }

• Adjust CSS nesting parser for IE7 hacks (#​3272)

  This fixes a regression with esbuild's treatment of IE7 hacks in CSS. CSS nesting allows selectors to be used where declarations are expected. There's an IE7 hack where prefixing a declaration with a * causes that declaration to only be applied in IE7 due to a bug in IE7's CSS parser. However, it's valid for nested CSS selectors to start with *. So esbuild was incorrectly parsing these declarations and anything following it up until the next { as a selector for a nested CSS rule. This release changes esbuild's parser to terminate the parsing of selectors for nested CSS rules when a ; is encountered to fix this edge case:

  /* Original code */
  .item {
    *width: 100%;
    height: 1px;
  }
  
  /* Old output */
  .item {
    *width: 100%; height: 1px; {
    }
  }
  
  /* New output */
  .item {
    *width: 100%;
    height: 1px;
  }

  Note that the syntax for CSS nesting is about to change again, so esbuild's CSS parser may still not be completely accurate with how browsers do and/or will interpret CSS nesting syntax. Expect additional updates to esbuild's CSS parser in the future to deal with upcoming CSS specification changes.

• Adjust esbuild's warning about undefined imports for TypeScript import equals declarations (#​3271)

  In JavaScript, accessing a missing property on an import namespace object is supposed to result in a value of undefined at run-time instead of an error at compile-time. This is something that esbuild warns you about by default because doing this can indicate a bug with your code. For example:

  // app.js
  import * as styles from './styles'
  console.log(styles.buton)

  // styles.js
  export let button = {}

  If you bundle app.js with esbuild you will get this:

  ▲ [WARNING] Import "buton" will always be undefined because there is no matching export in "styles.js" [import-is-undefined]
  
      app.js:2:19:
        2 │ console.log(styles.buton)
          │                    ~~~~~
          ╵                    button
  
    Did you mean to import "button" instead?
  
      styles.js:1:11:
        1 │ export let button = {}
          ╵            ~~~~~~
  

  However, there is TypeScript-only syntax for import equals declarations that can represent either a type import (which esbuild should ignore) or a value import (which esbuild should respect). Since esbuild doesn't have a type system, it tries to only respect import equals declarations that are actually used as values. Previously esbuild always generated this warning for unused imports referenced within import equals declarations even when the reference could be a type instead of a value. Starting with this release, esbuild will now only warn in this case if the import is actually used. Here is an example of some code that no longer causes an incorrect warning:

  // app.ts
  import * as styles from './styles'
  import ButtonType = styles.Button

  // styles.ts
  export interface Button {}

v0.18.16

Compare Source

• Fix a regression with whitespace inside :is() (#​3265)

  The change to parse the contents of :is() in version 0.18.14 introduced a regression that incorrectly flagged the contents as a syntax error if the contents started with a whitespace token (for example div:is( .foo ) {}). This regression has been fixed.

v0.18.15

Compare Source

• Add the --serve-fallback= option (#​2904)

  The web server built into esbuild serves the latest in-memory results of the configured build. If the requested path doesn't match any in-memory build result, esbuild also provides the --servedir= option to tell esbuild to serve the requested path from that directory instead. And if the requested path doesn't match either of those things, esbuild will either automatically generate a directory listing (for directories) or return a 404 error.

  Starting with this release, that last step can now be replaced with telling esbuild to serve a specific HTML file using the --serve-fallback= option. This can be used to provide a "not found" page for missing URLs. It can also be used to implement a single-page app that mutates the current URL and therefore requires the single app entry point to be served when the page is loaded regardless of whatever the current URL is.

• Use the tsconfig field in package.json during extends resolution (#​3247)

  This release adds a feature from TypeScript 3.2 where if a tsconfig.json file specifies a package name in the extends field and that package's package.json file has a tsconfig field, the contents of that field are used in the search for the base tsconfig.json file.

• Implement CSS nesting without :is() when possible (#​1945)

  Previously esbuild would always produce a warning when transforming nested CSS for a browser that doesn't support the :is() pseudo-class. This was because the nesting transform needs to generate an :is() in some complex cases which means the transformed CSS would then not work in that browser. However, the CSS nesting transform can often be done without generating an :is(). So with this release, esbuild will no longer warn when targeting browsers that don't support :is() in the cases where an :is() isn't needed to represent the nested CSS.

  In addition, esbuild's nested CSS transform has been updated to avoid generating an :is() in cases where an :is() is preferable but there's a longer alternative that is also equivalent. This update means esbuild can now generate a combinatorial explosion of CSS for complex CSS nesting syntax when targeting browsers that don't support :is(). This combinatorial explosion is necessary to accurately represent the original semantics. For example:

  /* Original code */
  .first,
  .second,
  .third {
    & > & {
      color: red;
    }
  }
  
  /* Old output (with --target=chrome80) */
  :is(.first, .second, .third) > :is(.first, .second, .third) {
    color: red;
  }
  
  /* New output (with --target=chrome80) */
  .first > .first,
  .first > .second,
  .first > .third,
  .second > .first,
  .second > .second,
  .second > .third,
  .third > .first,
  .third > .second,
  .third > .third {
    color: red;
  }

  This change means you can now use CSS nesting with esbuild when targeting an older browser that doesn't support :is(). You'll now only get a warning from esbuild if you use complex CSS nesting syntax that esbuild can't represent in that older browser without using :is(). There are two such cases:

  /* Case 1 */
  a b {
    .foo & {
      color: red;
    }
  }
  
  /* Case 2 */
  a {
    > b& {
      color: red;
    }
  }

  These two cases still need to use :is(), both for different reasons, and cannot be used when targeting an older browser that doesn't support :is():

  /* Case 1 */
  .foo :is(a b) {
    color: red;
  }
  
  /* Case 2 */
  a > a:is(b) {
    color: red;
  }

• Automatically lower inset in CSS for older browsers

  With this release, esbuild will now automatically expand the inset property to the top, right, bottom, and left properties when esbuild's target is set to a browser that doesn't support inset:

  /* Original code */
  .app {
    position: absolute;
    inset: 10px 20px;
  }
  
  /* Old output (with --target=chrome80) */
  .app {
    position: absolute;
    inset: 10px 20px;
  }
  
  /* New output (with --target=chrome80) */
  .app {
    position: absolute;
    top: 10px;
    right: 20px;
    bottom: 10px;
    left: 20px;
  }

• Add support for the new @starting-style CSS rule (#​3249)

  This at rule allow authors to start CSS transitions on first style update. That is, you can now make the transition take effect when the display property changes from none to block.

  /* Original code */
  @​starting-style {
    h1 {
      background-color: transparent;
    }
  }
  
  /* Output */
  @​starting-style{h1{background-color:transparent}}

  This was contributed by @​yisibl.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[github-actions]

🎉 This PR is included in version 6.0.6 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀