Bump esbuild from 0.18.6 to 0.18.16

[dependabot[bot]]

Bumps esbuild from 0.18.6 to 0.18.16.

Release notes

Sourced from esbuild's releases.

v0.18.16

• 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

• 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;
  }
  

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.18.16

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

0.18.15

• 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;
  

... (truncated)

Commits

• 2292036 publish 0.18.16 to npm
• 64f97bd fix #3266: support --analyze with --serve
• d645903 fix #3265: allow whitespace inside of :is()
• d514ba7 css: all tests now include output and warnings
• daf6473 publish 0.18.15 to npm
• 629c921 fix #3247: use tsconfig in package.json
• 60004e7 tsconfig tests: use consistent case
• 10826b7 make whitespace match surrounding code
• 73b2b52 feat: support CSS @​starting-style rule (#3249)
• ffb5ad1 add workflow_dispatch to ci
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov-commenter]

Codecov Report

Merging #339 (28f7f4e) into main (306893d) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #339   +/-   ##
=======================================
  Coverage   64.64%   64.64%           
=======================================
  Files          93       93           
  Lines        1533     1533           
  Branches      183      183           
=======================================
  Hits          991      991           
  Misses        529      529           
  Partials       13       13           

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

[dependabot[bot]]

Superseded by #340.