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.1
^20.12.7
->^20.17.10
^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.2
^8.57.0
->^8.57.1
^0.2.1
->^0.4.2
^1.21.0
->^1.21.7
^1.1.0
->^1.2.0
^0.30.9
->^0.30.17
^3.20240405.1
->^3.20241218.0
^1.6.1
->^1.7.3
^1.0.3
->^1.3.0
9.0.5
->9.15.1
^3.2.5
->^3.4.2
^4.14.2
->^4.29.1
^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.1
2024-12-15
Updates
test
withincludes
(#1787)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.2
Compare Source
Fix regression with
--define
andimport.meta
(#4010, #4012, #4013)The previous change in version 0.24.1 to use a more expression-like parser for
define
values to allow quoted property names introduced a regression that removed the ability to use--define:import.meta=...
. Even thoughimport
is normally a keyword that can't be used as an identifier, ES modules special-case theimport.meta
expression to behave like an identifier anyway. This change fixes the regression.This fix was contributed by @sapphi-red.
v0.24.1
Compare Source
Allow
es2024
as a target intsconfig.json
(#4004)TypeScript recently added
es2024
as a compilation target, so esbuild now supports this in thetarget
field oftsconfig.json
files, such as in the following configuration file:As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.
This fix was contributed by @billyjanitsch.
Allow automatic semicolon insertion after
get
/set
This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
Allow quoted property names in
--define
and--pure
(#4008)The
define
andpure
API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes--define
and--pure
consistent with--global-name
, which already supported quoted property names. For example, the following is now possible:Note that if you're passing values like this on the command line using esbuild's
--define
flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.Minify empty
try
/catch
/finally
blocks (#4003)With this release, esbuild will now attempt to minify empty
try
blocks:This can sometimes expose additional minification opportunities.
Include
entryPoint
metadata for thecopy
loader (#3985)Almost all entry points already include a
entryPoint
field in theoutputs
map in esbuild's build metadata. However, this wasn't the case for thecopy
loader as that loader is a special-case that doesn't behave like other loaders. This release adds theentryPoint
field in this case.Source mappings may now contain
null
entries (#3310, #3878)With this change, sources that result in an empty source map may now emit a
null
source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now thenull
mapping "resets" the source map so that any lookups into the minified code without any mappings resolves tonull
(which appears as the output file in stack traces) instead of the incorrect source file.This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.
Avoid using the parent directory name for determinism (#3998)
To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named
index.js
(or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all namedindex.js
but have unique directory names).This is problematic when the bundle entry point is named
index.js
and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now useindex
instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild'soutbase
API option, which defaults to the lowest common ancestor of all user-specified entry point paths.Experimental support for esbuild on NetBSD (#3974)
With this release, esbuild now has a published binary executable for NetBSD in the
@esbuild/netbsd-arm64
npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @bsiegert.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 in
Configuration
📅 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.