Bump esbuild from 0.13.8 to 0.13.9

[dependabot]

Bumps esbuild from 0.13.8 to 0.13.9.

Release notes

Sourced from esbuild's releases.

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
  $ 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)

... (truncated)

Changelog

Sourced from esbuild's changelog.

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

... (truncated)

Commits

• 9dc464a publish 0.13.9 to npm
• 62a3943 fix #1691: support "imports" in "package.json"
• aac02ae remove unused range
• 440896c resolver: rename "pe" => "pj"
• 6cc57fd check end-to-end test output
• 535445b add pnpm end-to-end tests
• 6f40235 fix #1703: handle silent "rename" syscall failure
• 2b52f3e add simple end-to-end tests
• 0c626c5 make yaml formatting consistent
• df08658 fix #1702: invalid css transform of border-radius
• See full diff 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)

[dependabot]

Superseded by #114.