chore(deps): update all non-major dependencies #20
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:
^20.11.24
->^20.11.30
^1.3.1
->^1.4.0
^0.3.6
->^0.3.7
^0.20.1
->^0.20.2
^14.0.0
->^14.1.0
^0.2.4
->^0.2.6
^5.3.3
->^5.4.3
^4.3.1
->^4.3.2
^1.3.1
->^1.4.0
Release Notes
vitest-dev/vitest (@vitest/coverage-v8)
v1.4.0
Compare Source
🚀 Features
not
- by @fenghan34 in https://github.com/vitest-dev/vitest/issues/5294 (b9d37)--project
option - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/5295 (201bd)shuffle.files
andshuffle.tests
options - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/5281 (356db)cache.dir
option - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/5229 (d7e8b)--changed
option - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5314 (600b4)clearScreen
cli flag - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5241 (e1735)🐞 Bug Fixes
--project
option - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/5265 (d1a06)--inspect-brk
to pause before execution - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5355 (e77c5)magic-string
tooptimizeDeps.include
- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5278 (8f04e)reportsDirectory
from removing user's project - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5376 (07ec3)toContain/toMatch
assertion error - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5267 (8ee59)defines
to supportundefined
values - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5284 (5b58b)onConsoleLog
return type - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5337 (6d1b1)beforeAll
andafterAll
- by @fenghan34 in https://github.com/vitest-dev/vitest/issues/5288 (ce5ca)@vitest/coverage-v8
are used - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5250 (29f98)View changes on GitHub
unjs/automd (automd)
v0.3.7
Compare Source
compare changes
🚀 Enhancements
bundlejs
(0ab578e)💅 Refactors
shields
by default (308381c)🏡 Chore
❤️ Contributors
evanw/esbuild (esbuild)
v0.20.2
Compare Source
Support TypeScript experimental decorators on
abstract
class fields (#3684)With this release, you can now use TypeScript experimental decorators on
abstract
class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:JSON loader now preserves
__proto__
properties (#3700)Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the
__proto__
key. A literal__proto__
property in a JavaScript object literal sets the prototype of the object instead of adding a property named__proto__
, while a literal__proto__
property in a JSON object literal just adds a property named__proto__
. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:Improve dead code removal of
switch
statements (#3659)With this release, esbuild will now remove
switch
statements in branches when minifying if they are known to never be evaluated:Empty enums should behave like an object literal (#3657)
TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated
undefined
instead of{}
for an empty enum. With this release, you can now use an empty enum to generate an empty object literal.Handle Yarn Plug'n'Play edge case with
tsconfig.json
(#3698)Previously a
tsconfig.json
file thatextends
another file in a package with anexports
map failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.Work around issues with Deno 1.31+ (#3682)
Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used
Deno.run
but that API is being removed in favor ofDeno.Command
. As part of this change, esbuild is now calling the newunref
function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild'sstop()
function to terminate the child process for Deno to be able to exit).However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with
error: Promise resolution is still pending but the event loop has already resolved
. It's unclear to me why this is happening. The call tounref
was recommended by someone on the Deno core team, and calling Node's equivalentunref
API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno'sunref
just works differently than Node'sunref
. In any case, it's not good for Deno tests that use esbuild to be failing.In this release, I am removing the call to
unref
to fix this issue. This means that you will now have to call esbuild'sstop()
function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced.Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding
setTimeout
calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding asetTimeout
was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno.markdown-it/markdown-it (markdown-it)
v14.1.0
Compare Source
Changed
Fixed
ije/md4w (md4w)
v0.2.6
Compare Source
v0.2.5
Compare Source
Microsoft/TypeScript (typescript)
v5.4.3
: TypeScript 5.4.3Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
v5.4.2
: TypeScript 5.4Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
aleclarson/vite-tsconfig-paths (vite-tsconfig-paths)
v4.3.2
Compare Source
Configuration
📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).
🚦 Automerge: Enabled.
♻ 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.