-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all non-major dependencies #42
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
changed the title
chore(deps): update dependency @types/node to v20.11.19
chore(deps): update all non-major dependencies
Feb 16, 2024
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 16, 2024 15:49
c7a3b20
to
981be74
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 16, 2024 19:45
981be74
to
1c0a07c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 17, 2024 22:52
1c0a07c
to
9487d5f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 19, 2024 09:50
9487d5f
to
e53c2f5
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 19, 2024 12:43
e53c2f5
to
4319e3b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 20, 2024 17:08
4319e3b
to
ec07a75
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 21, 2024 12:34
ec07a75
to
9c9e4cd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 22, 2024 23:24
9c9e4cd
to
c9344f3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 23, 2024 22:09
c9344f3
to
d338d55
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 24, 2024 16:50
d338d55
to
9c6affa
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 26, 2024 04:19
9c6affa
to
ad45d2d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 27, 2024 21:49
ad45d2d
to
93e18d3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 28, 2024 01:13
93e18d3
to
5ae7d60
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 24, 2024 11:20
b5ba829
to
68c11b7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 24, 2024 13:49
68c11b7
to
80ab203
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 27, 2024 08:42
80ab203
to
6fdd149
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 27, 2024 11:16
6fdd149
to
3597126
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 28, 2024 17:35
3597126
to
3a1a0a0
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 29, 2024 11:36
3a1a0a0
to
62c490f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 30, 2024 07:19
62c490f
to
c9411ff
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 1, 2024 12:32
c9411ff
to
ee17466
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 1, 2024 15:46
ee17466
to
5e9cf5b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 1, 2024 21:37
5e9cf5b
to
1763dcd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 2, 2024 13:38
1763dcd
to
deb17bc
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 2, 2024 22:43
deb17bc
to
7823c53
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 3, 2024 06:10
7823c53
to
ff06bec
Compare
Waleed-KH
approved these changes
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.1.2
->^20.1.4
^8.56.2
->^8.56.7
^20.11.18
->^20.12.3
^0.13.3
->^0.13.5
^0.20.0
->^0.20.2
8.15.3
->8.15.6
^4.11.0
->^4.14.0
^5.3.3
->^5.4.3
^7.4.0
->^7.5.0
^5.1.3
->^5.2.7
1.0.0-rc.42
->1.0.2
^1.2.2
->^1.4.0
^3.4.19
->^3.4.21
Release Notes
tsconfig/bases (@tsconfig/node20)
v20.1.4
Compare Source
v20.1.3
Compare Source
antfu/changelogithub (changelogithub)
v0.13.5
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.13.4
Compare Source
🐞 Bug Fixes
View changes on GitHub
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.v0.20.1
Compare Source
Fix a bug with the CSS nesting transform (#3648)
This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:
Constant folding for JavaScript inequality operators (#3645)
This release introduces constant folding for the
< > <= >=
operators. The minifier will now replace these operators withtrue
orfalse
when both sides are compile-time numeric or string constants:Better handling of
__proto__
edge cases (#3651)JavaScript object literal syntax contains a special case where a non-computed property with a key of
__proto__
sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:Fix cross-platform non-determinism with CSS color space transformations (#3650)
The Go compiler takes advantage of "fused multiply and add" (FMA) instructions on certain processors which do the operation
x*y + z
without intermediate rounding. This causes esbuild's CSS color space math to differ on different processors (currentlyppc64le
ands390x
), which breaks esbuild's guarantee of deterministic output. To avoid this, esbuild's color space math now inserts afloat64()
cast around every single math operation. This tells the Go compiler not to use the FMA optimization.Fix a crash when resolving a path from a directory that doesn't exist (#3634)
This release fixes a regression where esbuild could crash when resolving an absolute path if the source directory for the path resolution operation doesn't exist. While this situation doesn't normally come up, it could come up when running esbuild concurrently with another operation that mutates the file system as esbuild is doing a build (such as using
git
to switch branches). The underlying problem was a regression that was introduced in version 0.18.0.pnpm/pnpm (pnpm)
v8.15.6
Compare Source
Patch Changes
pnpm run
#7817.peerDependencies
#7813.--ignore-scripts
argument toprune
command #7836.Platinum Sponsors
Gold Sponsors
Silver Sponsors
v8.15.5
Compare Source
v8.15.4
Compare Source
rollup/rollup (rollup)
v4.14.0
Compare Source
2024-04-03
Features
Pull Requests
@shikiji/vitepress-twoslash
(@sapphi-red)v4.13.2
Compare Source
2024-03-28
Bug Fixes
Pull Requests
v4.13.1
Compare Source
2024-03-27
Bug Fixes
Pull Requests
v4.13.0
Compare Source
2024-03-12
Features
Pull Requests
v4.12.1
Compare Source
2024-03-06
Bug Fixes
Pull Requests
getRollupEror
togetRollupError
(@MrRefactoring)import.meta.ROLLUP_FILE_URL_referenceId
correctly (@sapphi-red)v4.12.0
Compare Source
2024-02-16
Features
Pull Requests
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:
typescript-eslint/typescript-eslint (typescript-eslint)
v7.5.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
vitejs/vite (vite)
v5.2.7
Compare Source
__vite__mapDeps
when it's not used (#16271) (890538a), closes #16271v5.2.6
Compare Source
fs.deny
with globs with directories (#16250) (ba5269c), closes #16250v5.2.5
Compare Source
v5.2.4
v5.2.3
optimizeDeps.include
glob syntax for./*
exports (#16230) (f184c80), closes #16230prepareStackTrace
(#16220) (dad7f4f), closes #16220utf8
replaced withutf-8
(#16232) (9800c73), closes #16232v5.2.2
v5.2.1
v5.2.0
,
inside query parameter of image URI in srcset property (#16081) (50caf67), closes #16081@shikiji/vitepress-twoslash
(#16168) (6f8a320), closes #16168v5.1.7
Compare Source
Please refer to CHANGELOG.md for details.
v5.1.6
Compare Source
v5.1.5
Compare Source
__vite__mapDeps
code injection (#15732) (aff54e1), closes #15732experimentalDecorators: true
(#15206) (4144781), closes #15206pathe
(#16061) (aac2ef7), closes #16061v5.1.4
Compare Source
fs.cachedChecks: true
(#15983) (4fe971f), closes #15983vuejs/vitepress (vitepress)
v1.0.2
Compare Source
Bug Fixes
v1.0.1
Compare Source
Bug Fixes
v1.0.0
Compare Source
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.