Bump esbuild from 0.8.46 to 0.9.7

[dependabot]

Bumps esbuild from 0.8.46 to 0.9.7.

Release notes

Sourced from esbuild's releases.

v0.9.7

• Add support for Android on ARM 64-bit (#803)

  This release includes support for Android in the official esbuild package. It should now be possible to install and run esbuild on Android devices through npm.

• Fix incorrect MIME types on Windows (#1030)

  The web server built into esbuild uses the file extension to determine the value of the Content-Type header. This was previously done using the mime.TypeByExtension() function from Go's standard library. However, this function is apparently broken on Windows because installed programs can change MIME types in the Windows registry: golang/go#32350. This release fixes the problem by using a copy of Go's mime.TypeByExtension() function without the part that reads from the Windows registry.

• Using a top-level return inside an ECMAScript module is now forbidden

  The CommonJS module format is implemented as an anonymous function wrapper, so technically you can use a top-level return statement and it will actually work. Some packages in the wild use this to exit early from module initialization, so esbuild supports this. However, the ECMAScript module format doesn't allow top-level returns. With this release, esbuild no longer allows top-level returns in ECMAScript modules.

v0.9.6

• Expose build options to plugins (#373)

  Plugins can now access build options from within the plugin using the initialOptions property. For example:

  let nodeEnvPlugin = {
    name: 'node-env',
    setup(build) {
      const options = build.initialOptions
      options.define = options.define || {}
      options.define['process.env.NODE_ENV'] =
        options.minify ? '"production"' : '"development"'
    },
  }

• Fix an edge case with the object spread transform (#1017)

  This release fixes esbuild's object spread transform in cases where property assignment could be different than property definition. For example:

  console.log({
    get x() {},
    ...{x: 1},
  })

  This should print {x: 1} but transforming this through esbuild with --target=es6 causes the resulting code to throw an error. The problem is that esbuild currently transforms this code to a call to Object.assign and that uses property assignment semantics, which causes the assignment to throw (since you can't assign to a getter-only property).

  With this release, esbuild will now transform this into code that manually loops over the properties and copies them over one-by-one using Object.defineProperty instead. This uses property definition semantics which better matches the specification.

• Fix a TypeScript parsing edge case with arrow function return types (#1016)

  This release fixes the following TypeScript parsing edge case:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.9.7

• Add support for Android on ARM 64-bit (#803)

  This release includes support for Android in the official esbuild package. It should now be possible to install and run esbuild on Android devices through npm.

• Fix incorrect MIME types on Windows (#1030)

  The web server built into esbuild uses the file extension to determine the value of the Content-Type header. This was previously done using the mime.TypeByExtension() function from Go's standard library. However, this function is apparently broken on Windows because installed programs can change MIME types in the Windows registry: golang/go#32350. This release fixes the problem by using a copy of Go's mime.TypeByExtension() function without the part that reads from the Windows registry.

• Using a top-level return inside an ECMAScript module is now forbidden

  The CommonJS module format is implemented as an anonymous function wrapper, so technically you can use a top-level return statement and it will actually work. Some packages in the wild use this to exit early from module initialization, so esbuild supports this. However, the ECMAScript module format doesn't allow top-level returns. With this release, esbuild no longer allows top-level returns in ECMAScript modules.

0.9.6

• Expose build options to plugins (#373)

  Plugins can now access build options from within the plugin using the initialOptions property. For example:

  let nodeEnvPlugin = {
    name: 'node-env',
    setup(build) {
      const options = build.initialOptions
      options.define = options.define || {}
      options.define['process.env.NODE_ENV'] =
        options.minify ? '"production"' : '"development"'
    },
  }

• Fix an edge case with the object spread transform (#1017)

  This release fixes esbuild's object spread transform in cases where property assignment could be different than property definition. For example:

  console.log({
    get x() {},
    ...{x: 1},
  })

  This should print {x: 1} but transforming this through esbuild with --target=es6 causes the resulting code to throw an error. The problem is that esbuild currently transforms this code to a call to Object.assign and that uses property assignment semantics, which causes the assignment to throw (since you can't assign to a getter-only property).

  With this release, esbuild will now transform this into code that manually loops over the properties and copies them over one-by-one using Object.defineProperty instead. This uses property definition semantics which better matches the specification.

• Fix a TypeScript parsing edge case with arrow function return types (#1016)

  This release fixes the following TypeScript parsing edge case:

... (truncated)

Commits

• c7ea6ce publish 0.9.7 to npm
• 3da3361 fix #803: add support for android arm64
• 0a0cbfb fix comments (#1046)
• e249c17 fix #1039: lazily capture plugin register traces
• c8eb58f fix #1030: work around a bug in go's mime types
• 03f176c fix browser test
• b2249a2 forbid top-level returns in ESM
• 3c679d5 publish 0.9.6 to npm
• d790be4 fix #373: expose build options to plugins
• d012ce1 implement recent v8 changes to optional chaining behavior (#1022)
• 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)

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/monkatraz/mainframe/GyaRzTSsAscmotuZCuBTDxRkpa46
✅ Preview: https://mainframe-git-dependabot-npmandyarnesbuild-097-monkatraz.vercel.app

[dependabot]

Superseded by #163.