Bump esbuild from 0.13.8 to 0.13.10

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps esbuild from 0.13.8 to 0.13.10.

Release notes

Sourced from esbuild's releases.

v0.13.10

• 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

• 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
  

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.13.10

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

0.13.9

• 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')
  

... (truncated)

Commits

• df3e9c2 publish 0.13.10 to npm
• 3f28da8 add ".mts" and ".cts" to exports kind checking
• 937ec5a update to unicode 14
• 91b8a21 fix #1539: implement legal comments for css
• 1be3582 Allow target for ES-Version to be uppercase (#1718)
• 5f558d4 update the compat table
• fb1fe9e remove invalid "es7" option in tsconfig parser
• 6be55d8 link from code to docs for vs code autocomplete
• 77d6a5e update @​next targets for npm and yarn
• 412f976 add "check out code" to old go version 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)