chore(deps-dev): bump esbuild from 0.14.51 to 0.14.53

[dependabot]

Bumps esbuild from 0.14.51 to 0.14.53.

Release notes

Sourced from esbuild's releases.

v0.14.53

This release fixes a minor issue with the previous release: I had to rename the package esbuild-linux-loong64 to @esbuild/linux-loong64 in the contributed PR because someone registered the package name before I could claim it, and I missed a spot. Hopefully everything is working after this release. I plan to change all platform-specific package names to use the @esbuild/ scope at some point to avoid this problem in the future.

v0.14.52

• Allow binary data as input to the JS transform and build APIs (#2424)

  Previously esbuild's transform and build APIs could only take a string. However, some people want to use esbuild to convert binary data to base64 text. This is problematic because JavaScript strings represent UTF-16 text and esbuild internally operates on arrays of bytes, so all strings coming from JavaScript undergo UTF-16 to UTF-8 conversion before use. This meant that using esbuild in this way was doing base64 encoding of the UTF-8 encoding of the text, which was undesired.

  With this release, esbuild now accepts Uint8Array in addition to string as an input format for the transform and build APIs. Now you can use esbuild to convert binary data to base64 text:

  // Original code
  import esbuild from 'esbuild'
  console.log([
    (await esbuild.transform('\xFF', { loader: 'base64' })).code,
    (await esbuild.build({ stdin: { contents: '\xFF', loader: 'base64' }, write: false })).outputFiles[0].text,
  ])
  console.log([
    (await esbuild.transform(new Uint8Array([0xFF]), { loader: 'base64' })).code,
    (await esbuild.build({ stdin: { contents: new Uint8Array([0xFF]), loader: 'base64' }, write: false })).outputFiles[0].text,
  ])
  // Old output
  [ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
  /* ERROR: The input to "transform" must be a string */
  // New output
  [ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
  [ 'module.exports = "/w==";\n', 'module.exports = "/w==";\n' ]

• Update the getter for text in build results (#2423)

  Output files in build results returned from esbuild's JavaScript API have both a contents and a text property to return the contents of the output file. The contents property is a binary UTF-8 Uint8Array and the text property is a JavaScript UTF-16 string. The text property is a getter that does the UTF-8 to UTF-16 conversion only if it's needed for better performance.

  Previously if you mutate the build results object, you had to overwrite both contents and text since the value returned from the text getter is the original text returned by esbuild. Some people find this confusing so with this release, the getter for text has been updated to do the UTF-8 to UTF-16 conversion on the current value of the contents property instead of the original value.

• Publish builds for Linux LoongArch 64-bit (#1804, #2373)

  This release upgrades to Go 1.19, which now includes support for LoongArch 64-bit processors. LoongArch 64-bit builds of esbuild will now be published to npm, which means that in theory they can now be installed with npm install esbuild. This was contributed by @​beyond-1234.

Changelog

Sourced from esbuild's changelog.

0.14.53

This release fixes a minor issue with the previous release: I had to rename the package esbuild-linux-loong64 to @esbuild/linux-loong64 in the contributed PR because someone registered the package name before I could claim it, and I missed a spot. Hopefully everything is working after this release. I plan to change all platform-specific package names to use the @esbuild/ scope at some point to avoid this problem in the future.

0.14.52

• Allow binary data as input to the JS transform and build APIs (#2424)

  Previously esbuild's transform and build APIs could only take a string. However, some people want to use esbuild to convert binary data to base64 text. This is problematic because JavaScript strings represent UTF-16 text and esbuild internally operates on arrays of bytes, so all strings coming from JavaScript undergo UTF-16 to UTF-8 conversion before use. This meant that using esbuild in this way was doing base64 encoding of the UTF-8 encoding of the text, which was undesired.

  With this release, esbuild now accepts Uint8Array in addition to string as an input format for the transform and build APIs. Now you can use esbuild to convert binary data to base64 text:

  // Original code
  import esbuild from 'esbuild'
  console.log([
    (await esbuild.transform('\xFF', { loader: 'base64' })).code,
    (await esbuild.build({ stdin: { contents: '\xFF', loader: 'base64' }, write: false })).outputFiles[0].text,
  ])
  console.log([
    (await esbuild.transform(new Uint8Array([0xFF]), { loader: 'base64' })).code,
    (await esbuild.build({ stdin: { contents: new Uint8Array([0xFF]), loader: 'base64' }, write: false })).outputFiles[0].text,
  ])
  // Old output
  [ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
  /* ERROR: The input to "transform" must be a string */
  // New output
  [ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
  [ 'module.exports = "/w==";\n', 'module.exports = "/w==";\n' ]

• Update the getter for text in build results (#2423)

  Output files in build results returned from esbuild's JavaScript API have both a contents and a text property to return the contents of the output file. The contents property is a binary UTF-8 Uint8Array and the text property is a JavaScript UTF-16 string. The text property is a getter that does the UTF-8 to UTF-16 conversion only if it's needed for better performance.

  Previously if you mutate the build results object, you had to overwrite both contents and text since the value returned from the text getter is the original text returned by esbuild. Some people find this confusing so with this release, the getter for text has been updated to do the UTF-8 to UTF-16 conversion on the current value of the contents property instead of the original value.

• Publish builds for Linux LoongArch 64-bit (#1804, #2373)

  This release upgrades to Go 1.19, which now includes support for LoongArch 64-bit processors. LoongArch 64-bit builds of esbuild will now be published to npm, which means that in theory they can now be installed with npm install esbuild. This was contributed by @​beyond-1234.

Commits

• 4e65c73 publish 0.14.53 to npm
• adbb475 missed two esbuild-linux-loong64 names
• 39eccb8 publish 0.14.52 to npm
• d6cf390 Support Loongarch LE architecture (#2373)
• 296870e workarounds for bad go comment formatting behavior
• af0ab3e run the new go formatter, which mangles comments
• 21deb41 update go 1.18.4 => 1.19
• ea63c87 add a note about go 1.13 (#2431)
• 7bd4900 Revert "fix #2417: autmatically add module to conditions"
• 5e918f4 fix #2417: autmatically add module to conditions
• 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)