chore(deps): update devdependencies #1222
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~10.3.1
->~10.4.0
~0.14.51
->~0.14.53
Release Notes
cypress-io/cypress
v10.4.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#​10-4-0
evanw/esbuild
v0.14.53
Compare Source
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
Compare Source
Allow binary data as input to the JS
transform
andbuild
APIs (#2424)Previously esbuild's
transform
andbuild
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 thetransform
andbuild
APIs. Now you can use esbuild to convert binary data to base64 text: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 atext
property to return the contents of the output file. Thecontents
property is a binary UTF-8 Uint8Array and thetext
property is a JavaScript UTF-16 string. Thetext
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
andtext
since the value returned from thetext
getter is the original text returned by esbuild. Some people find this confusing so with this release, the getter fortext
has been updated to do the UTF-8 to UTF-16 conversion on the current value of thecontents
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.Configuration
📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.