chore(deps): update all non-major dependencies #32
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:
^15.2.3
->^15.3.0
^20.12.7
->^20.17.9
^1.5.0
->^1.6.0
1.12.1
->1.14.1
1.12.1
->1.14.1
1.12.1
->1.14.1
1.12.1
->1.14.1
^1.12.1
->^1.14.1
^0.27.27
->^0.27.31
^0.3.7
->^0.3.12
^0.5.5
->^0.5.7
^0.20.2
->^0.24.0
^8.57.0
->^8.57.1
^0.2.1
->^0.4.2
^1.21.0
->^1.21.6
^0.30.9
->^0.30.14
^3.20240405.1
->^3.20241106.1
^1.6.1
->^1.7.3
^1.0.3
->^1.2.1
9.0.5
->9.14.4
^3.2.5
->^3.4.1
^4.14.2
->^4.28.0
^5.4.5
->^5.7.2
^1.10.1
->^1.16.0
^5.2.8
->^5.4.11
^1.5.0
->^1.6.0
Release Notes
rollup/plugins (@rollup/plugin-node-resolve)
v15.3.0
2024-09-23
Features
v15.2.4
2024-09-22
Updates
vitest-dev/vitest (@vitest/coverage-v8)
v1.6.0
Compare Source
🚀 Features
includeConsoleOutput
andaddFileAttribute
in junit - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5659 (2f913)🐞 Bug Fixes
resolveId('vitest')
afterbuildStart
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5646 (f5faf)toJSON
for error serialization - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5526 (19a21)*.test-d.*
by default - by @MindfulPol in https://github.com/vitest-dev/vitest/issues/5634 (bfe8a)vite-node
's wrapper only to executed files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5642 (c9883)🏎 Performance
View changes on GitHub
v1.5.3
Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.5.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.5.1
Compare Source
🚀 Features
startVitest()
to acceptstdout
andstdin
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5493 (780b1)startVitest
API is experimental and doesn't follow semver.🐞 Bug Fixes
import.meta.env.PROD: false
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5561 (9c649)onTestFinished
in reverse order - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5598 (23f29)fileParallelism
by default on browser pool - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5528 (5c69f)v8-to-istanbul
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5549 (df6a4)cleanOnRerun
is disabled - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5540 (ea3c1)thresholds
to compare files relative to root - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5574 (80265)toEqual
andtoMatchObject
with circular references - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5535 (9e641)View changes on GitHub
xtuc/webassemblyjs (@webassemblyjs/helper-wasm-bytecode)
v1.14.1
Compare Source
v1.14.0
Compare Source
v1.13.2
Compare Source
v1.13.1
Compare Source
v1.13.0
Compare Source
xtuc/webassemblyjs (@webassemblyjs/ieee754)
v1.14.1
Compare Source
v1.14.0
Compare Source
v1.13.2
Compare Source
v1.13.1
Compare Source
v1.13.0
Compare Source
xtuc/webassemblyjs (@webassemblyjs/leb128)
v1.14.1
Compare Source
v1.14.0
Compare Source
v1.13.2
Compare Source
v1.13.1
Compare Source
v1.13.0
Compare Source
AssemblyScript/assemblyscript (assemblyscript)
v0.27.31
Compare Source
New features
285afb1
)Other
e763f78
)d6f09f4
)Signed-off-by: longxiangqiao [email protected]
tlsfvis.html
label issue (#2881) (15b1c30
)1554258
)v0.27.30
Compare Source
Bug fixes
dfc8a65
)Operator overload is an internal mechanism, it can support to compare user-defined class, but it need to be limited.
a == b
andb == a
should run the same function and get the same result in semantic level. Allowing ambiguity is bug prone.1847c8f
)Other
4bd1c12
)v0.27.29
Compare Source
Bug fixes
f79391c
)Other
acdb242
)v0.27.28
Compare Source
Bug fixes
78963c5
)Other
be49610
)unjs/automd (automd)
v0.3.12
Compare Source
compare changes
🩹 Fixes
❤️ Contributors
v0.3.11
Compare Source
compare changes
🩹 Fixes
🏡 Chore
lint:fix
script (1ed252e)❤️ Contributors
v0.3.10
Compare Source
compare changes
💅 Refactors
npm.chart.dev
for npm downloads (#75)🏡 Chore
❤️ Contributors
v0.3.9
Compare Source
compare changes
🚀 Enhancements
🏡 Chore
❤️ Contributors
v0.3.8
Compare Source
compare changes
🚀 Enhancements
🩹 Fixes
version
should be obtained automatically when set totrue
(#59)📖 Documentation
🏡 Chore
❤️ Contributors
unjs/changelogen (changelogen)
v0.5.7
Compare Source
compare changes
🩹 Fixes
+
for canary suffix (#224)❤️ Contributors
v0.5.6
Compare Source
compare changes
🚀 Enhancements
🩹 Fixes
💅 Refactors
execa
withexecSync
(#222)🏡 Chore
❤️ Contributors
evanw/esbuild (esbuild)
v0.24.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.23.0
or~0.23.0
. See npm's documentation about semver for more information.Drop support for older platforms (#3902)
This release drops support for the following operating system:
This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.
Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:
Fix class field decorators in TypeScript if
useDefineForClassFields
isfalse
(#3913)Setting the
useDefineForClassFields
flag tofalse
intsconfig.json
means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.Avoid incorrect cycle warning with
tsconfig.json
multiple inheritance (#3898)TypeScript 5.0 introduced multiple inheritance for
tsconfig.json
files whereextends
can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release,tsconfig.json
files containing this edge case should work correctly without generating a warning.Handle Yarn Plug'n'Play stack overflow with
tsconfig.json
(#3915)Previously a
tsconfig.json
file thatextends
another file in a package with anexports
map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.Work around more issues with Deno 1.31+ (#3917)
This version of Deno broke the
stdin
andstdout
properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. whenimport.meta.main
istrue
). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.This fix was contributed by @Joshix-1.
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.v0.23.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.22.0
or~0.22.0
. See npm's documentation about semver for more information.Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made
--packages=external
the default behavior with--platform=node
. The default is now back to--packages=bundle
.I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
Fix preserving collapsed JSX whitespace (#3818)
When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with
--jsx=preserve
. Here is an example:v0.22.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.21.0
or~0.21.0
. See npm's documentation about semver for more information.Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for
--platform=node
) because some packages may not be intended for bundlers, and may uConfiguration
📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.