fix(deps): update dependency esbuild to v0.23.1 #233
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:
0.23.0
->0.23.1
Release Notes
evanw/esbuild (esbuild)
v0.23.1
Compare Source
Allow using the
node:
import prefix withes*
targets (#3821)The
node:
prefix on imports is an alternate way to import built-in node modules. For example,import fs from "fs"
can also be writtenimport fs from "node:fs"
. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with--target=node14
so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as--target=node18,es2022
removes thenode:
prefix because none of thees*
targets are known to support this feature. This release adds the support for thenode:
flag to esbuild's internal compatibility table fores*
to allow you to use compound targets like this:Fix a panic when using the CLI with invalid build flags if
--analyze
is present (#3834)Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the
--analyze
flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how--analyze
is implemented) to a null build object. The panic has been fixed in this release.Fix incorrect location of certain error messages (#3845)
This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
Print comments before case clauses in switch statements (#3838)
With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
Fix a memory leak with
pluginData
(#3825)With this release, the build context's internal
pluginData
cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that returnpluginData
objects fromonResolve
and/oronLoad
callbacks.Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.