-
Notifications
You must be signed in to change notification settings - Fork 2
chore(deps): update non-major (static) #224
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
base: static
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
f117945 to
b359b1d
Compare
b359b1d to
5dc28de
Compare
5dc28de to
4769150
Compare
4769150 to
cdfdbbc
Compare
cdfdbbc to
aecf1d8
Compare
aecf1d8 to
8487480
Compare
8487480 to
4de221d
Compare
4de221d to
5cf372c
Compare
5cf372c to
6231f21
Compare
6231f21 to
88253ca
Compare
88253ca to
d0ca623
Compare
d0ca623 to
60b2f12
Compare
0f51478 to
387e509
Compare
387e509 to
cde00c7
Compare
cde00c7 to
980a96b
Compare
980a96b to
2b10088
Compare
2b10088 to
d42452c
Compare
d42452c to
a884caa
Compare
a884caa to
cd57516
Compare
cd57516 to
b4d50bc
Compare
b4d50bc to
82a71d3
Compare
82a71d3 to
6e925e7
Compare
6e925e7 to
77ad84a
Compare
77ad84a to
bb91cde
Compare
bb91cde to
be0c83e
Compare
be0c83e to
d5d8bc4
Compare
This PR contains the following updates:
^0.5.1→^0.5.2^2.29.7→^2.29.8^8.1.21→^8.1.29^2.0.1→^2.0.34.0.0-static.38→4.0.0-static.46^1.5.5→^1.5.6^5.0.3→^5.0.6^4.17.20→^4.17.23^20.19.21→^20.19.30^19.2.2→^19.2.8^19.2.2→^19.2.3^1.17.4→^1.18.0^5.1.1→^5.1.4^5.0.4→^5.1.2^4.11.0→^4.11.1^0.25.11→^0.27.2^5.5.4→^5.5.5^5.1.0→^5.2.1271a8d0→22a9089^3.6.2→^3.8.0^19.2.0→^19.2.3^19.2.0→^19.2.3^19.2.0→^19.2.3^7.1.10→^7.3.1Release Notes
changesets/changesets (@changesets/changelog-github)
v0.5.2Compare Source
sanity-io/pkg-utils (@sanity/pkg-utils)
v8.1.29Compare Source
Bug Fixes
v8.1.28Compare Source
Bug Fixes
v8.1.27Compare Source
Bug Fixes
v8.1.26Compare Source
Bug Fixes
v8.1.25Compare Source
Bug Fixes
v8.1.24Compare Source
Bug Fixes
v8.1.23Compare Source
Bug Fixes
v8.1.22Compare Source
Bug Fixes
sanity-io/prettier-config (@sanity/prettier-config)
v2.0.3Compare Source
Bug Fixes
v2.0.2Compare Source
Bug Fixes
sanity-io/ui (@sanity/ui)
v4.0.0-static.46Compare Source
Bug Fixes
<Activity>on<Tooltip>&<Popover>" (2d7050f)Reverts
This release is also available on:
v4.0.0-static.45Compare Source
Features
<Activity>on<Tooltip>&<Popover>(a20335f)This release is also available on:
v4.0.0-static.44Compare Source
Bug Fixes
useEffectEvent(e75f30b)This release is also available on:
v4.0.0-static.43Compare Source
Bug Fixes
This release is also available on:
v4.0.0-static.42Compare Source
Bug Fixes
framer-motionwithmotion/react(9a95ffd)This release is also available on:
v4.0.0-static.41Compare Source
Bug Fixes
This release is also available on:
v4.0.0-static.40Compare Source
Bug Fixes
duration: Infinity(d6f7c61)This release is also available on:
v4.0.0-static.39Compare Source
Bug Fixes
This release is also available on:
vanilla-extract-css/vanilla-extract (@vanilla-extract/css)
v1.18.0Compare Source
Minor Changes
#1566
8b49b35Thanks @lfantone! -style: Add support for@starting-stylerulesEXAMPLE USAGE:
Patch Changes
#1646
0b2c09eThanks @plesiecki! - Swap the order ofcreateVar's overloads to enable inference ofVarDelcarationtype#1666
c6047fbThanks @askoufis! - Remove custom container properties typeThe
csstypepackage used by Vanilla Extract now provides types for container properties, so the custom type definitions that were previously necessary have been removed.v1.17.5Compare Source
Patch Changes
11a7c66Thanks @askoufis! - Updatecsstypedependency to^3.2.3vanilla-extract-css/vanilla-extract (@vanilla-extract/vite-plugin)
v5.1.4Compare Source
Patch Changes
#1665
352fc19Thanks @askoufis! - Assets used in CSS generated by the plugin will now respect thebuild.assetsInlineLimitVite configuration optionUpdated dependencies [
a440470,352fc19]:v5.1.3Compare Source
Patch Changes
v5.1.2Compare Source
Patch Changes
46ef1db,ad5a08b]:vitejs/vite-plugin-react (@vitejs/plugin-react)
v5.1.2Compare Source
v5.1.1Compare Source
Update code to support newer
rolldown-vite(#976)rolldown-vitewill removeoptimizeDeps.rollupOptionsin favor ofoptimizeDeps.rolldownOptionssoon. This plugin now usesoptimizeDeps.rolldownOptionsto support newerrolldown-vite. Please updaterolldown-viteto the latest version if you are using an older version.v5.1.0Compare Source
Add
@vitejs/plugin-react/preamblevirtual module for SSR HMR (#890)SSR applications can now initialize HMR runtime by importing
@vitejs/plugin-react/preambleat the top of their client entry instead of manually callingtransformIndexHtml. This simplifies SSR setup for applications that don't use thetransformIndexHtmlAPI.Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#930)
Rolldown 1.0.0-beta.44+ removed the top-level
jsxoption in favor oftransform.jsx. This plugin now uses thetransform.jsxoption to support Rolldown 1.0.0-beta.44+.dequelabs/axe-core (axe-core)
v4.11.1Compare Source
evanw/esbuild (esbuild)
v0.27.2Compare Source
Allow import path specifiers starting with
#/(#4361)Previously the specification for
package.jsondisallowed import path specifiers starting with#/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping#/*to./src/*(previously you had to use another character such as#_*instead, which was more confusing). There is some more context in nodejs/node#49182.This change was contributed by @hybrist.
Automatically add the
-webkit-maskprefix (#4357, #4358)This release automatically adds the
-webkit-vendor prefix for themaskCSS shorthand property:This change was contributed by @BPJEnnova.
Additional minification of
switchstatements (#4176, #4359)This release contains additional minification patterns for reducing
switchstatements. Here is an example:Forbid
usingdeclarations insideswitchclauses (#4323)This is a rare change to remove something that was previously possible. The Explicit Resource Management proposal introduced
usingdeclarations. These were previously allowed insidecaseanddefaultclauses inswitchstatements. This had well-defined semantics and was already widely implemented (by V8, SpiderMonkey, TypeScript, esbuild, and others). However, it was considered to be too confusing because of how scope works in switch statements, so it has been removed from the specification. This edge case will now be a syntax error. See tc39/proposal-explicit-resource-management#215 and rbuckton/ecma262#14 for details.Here is an example of code that is no longer allowed:
That code will now have to be modified to look like this instead (note the additional
{and}block statements around each case body):This is not being released in one of esbuild's breaking change releases since this feature hasn't been finalized yet, and esbuild always tracks the current state of the specification (so esbuild's previous behavior was arguably incorrect).
v0.27.1Compare Source
Fix bundler bug with
varnested insideif(#4348)This release fixes a bug with the bundler that happens when importing an ES module using
require(which causes it to be wrapped) and there's a top-levelvarinside anifstatement without being wrapped in a{ ... }block (and a few other conditions). The bundling transform needed to hoist thesevardeclarations outside of the lazy ES module wrapper for correctness. See the issue for details.Fix minifier bug with
forinsidetryinside label (#4351)This fixes an old regression from version v0.21.4. Some code was introduced to move the label inside the
trystatement to address a problem with transforming labeledfor awaitloops to avoid theawait(the transformation involves converting thefor awaitloop into aforloop and wrapping it in atrystatement). However, it introduces problems for cross-compiled JVM code that uses all three of these features heavily. This release restricts this transform to only apply toforloops that esbuild itself generates internally as part of thefor awaittransform. Here is an example of some affected code:Inline IIFEs containing a single expression (#4354)
Previously inlining of IIFEs (immediately-invoked function expressions) only worked if the body contained a single
returnstatement. Now it should also work if the body contains a single expression statement instead:The minifier now strips empty
finallyclauses (#4353)This improvement means that
finallyclauses containing dead code can potentially cause the associatedtrystatement to be removed from the output entirely in minified builds:Allow tree-shaking of the
SymbolconstructorWith this release, calling
Symbolis now considered to be side-effect free when the argument is known to be a primitive value. This means esbuild can now tree-shake module-level symbol variables:v0.27.0Compare 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
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.26.0or~0.26.0. See npm's documentation about semver for more information.Use
Uint8Array.fromBase64if available (#4286)With this release, esbuild's
binaryloader will now use the newUint8Array.fromBase64function unless it's unavailable in the configured target environment. If it's unavailable, esbuild's previous code for this will be used as a fallback. Note that this means you may now need to specifytargetwhen using this feature with Node (for example--target=node22) unless you're using Node v25+.Update the Go compiler from v1.23.12 to v1.25.4 (#4208, #4311)
This raises the operating system requirements for running esbuild:
v0.26.0Compare Source
Enable trusted publishing (#4281)
GitHub and npm are recommending that maintainers for packages such as esbuild switch to trusted publishing. With this release, a VM on GitHub will now build and publish all of esbuild's packages to npm instead of me. In theory.
Unfortunately there isn't really a way to test that this works other than to do it live. So this release is that live test. Hopefully this release is uneventful and is exactly the same as the previous one (well, except for the green provenance attestation checkmark on npm that happens with trusted publishing).
v0.25.12Compare Source
Fix a minification regression with CSS media queries (#4315)
The previous release introduced support for parsing media queries which unintentionally introduced a regression with the removal of duplicate media rules during minification. Specifically the grammar for
@media <media-type> and <media-condition-without-or> { ... }was missing an equality check for the<media-condition-without-or>part, so rules with different suffix clauses in this position would incorrectly compare equal and be deduplicated. This release fixes the regression.Update the list of known JavaScript globals (#4310)
This release updates esbuild's internal list of known JavaScript globals. These are globals that are known to not have side-effects when the property is accessed. For example, accessing the global
Arrayproperty is considered to be side-effect free but accessing the globalscrollYproperty can trigger a layout, which is a side-effect. This is used by esbuild's tree-shaking to safely remove unused code that is known to be side-effect free. This update adds the following global properties:From ES2017:
AtomicsSharedArrayBufferFrom ES2020:
BigInt64ArrayBigUint64ArrayFrom ES2021:
FinalizationRegistryWeakRefFrom ES2025:
Float16ArrayIteratorNote that this does not indicate that constructing any of these objects is side-effect free, just that accessing the identifier is side-effect free. For example, this now allows esbuild to tree-shake classes that extend from
Iterator:Add support for the new
@view-transitionCSS rule (#4313)With this release, esbuild now has improved support for pretty-printing and minifying the new
@view-transitionrule (which esbuild was previously unaware of):The new view transition feature provides a mechanism for creating animated transitions between documents in a multi-page app. You can read more about view transition rules here.
This change was contributed by @yisibl.
Trim CSS rules that will never match
The CSS minifier will now remove rules whose selectors contain
:is()and:where()as those selectors will never match. These selectors can currently be automatically generated by esbuild when you give esbuild nonsensical input such as the following:This input is nonsensical because CSS nesting is (unfortunately) not supported inside of pseudo-elements such as
:before. Currently esbuild generates a rule containing:is()in this case when you tell esbuild to transform nested CSS into non-nested CSS. I think it's reasonable to do that as it sort of helps explain what's going on (or at least indicates that something is wrong in the output). It shouldn't be present in minified code, however, so this release now strips it out.prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.5.5Compare Source
Patch Changes
#772
7264ed0Thanks @BPScott! - Bump prettier-linter-helpers dependency to v1.0.1#776
77651a3Thanks @aswils! - fix: bump synckit for yarn PnP ESM issueexpressjs/express (express)
v5.2.1Compare Source
=======================
v5.2.0Compare Source
========================
body-parser@^2.2.1res.redirectwith undefined arguments, Express now emits a warning to help detect calls that pass undefined as the status or URL and make them easier to fix.prettier/prettier (prettier)
v3.8.0Compare Source
diff
🔗 Release note
v3.7.4Compare Source
diff
LWC: Avoid quote around interpolations (#18383 by @kovsu)
TypeScript: Fix comment inside union type gets duplicated (#18393 by @fisker)
TypeScript: Fix unstable comment print in union type comments (#18395 by @fisker)
v3.7.3Compare Source
diff
API: Fix
prettier.getFileInfo()change that breaks VSCode extension (#18375 by @fisker)An internal refactor accidentally broke the VSCode extension plugin loading.
v3.7.2Compare Source
diff
JavaScript: Fix string print when switching quotes (#18351 by @fisker)
JavaScript: Preserve quote for embedded HTML attribute values (#18352 by @kovsu)
TypeScript: Fix comment in empty type literal (#18364 by @fisker)
v3.7.1Compare Source
diff
API: Fix performance regression in doc printer (#18342 by @fisker)
Prettier 3.7.1 can be very slow when formatting big files, the regression has been fixed.
v3.7.0Compare Source
diff
🔗 Release Notes
facebook/react (react)
v19.2.3: 19.2.3 (December 11th, 2025)Compare Source
React Server Components
v19.2.2: 19.2.2 (December 11th, 2025)Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon #35290)v19.2.1: 19.2.1 (December 3rd, 2025)Compare Source
React Server Components
vitejs/vite (vite)
v7.3.1Compare Source
Please refer to CHANGELOG.md for details.
v7.3.0Compare Source
Please refer to CHANGELOG.md for details.
v7.2.7Compare Source
v7.2.6Compare Source
7.2.6 (2025-12-01)
v7.2.4Compare Source
Bug Fixes
v7.2.3[Compare Source](https://redirect.github.com/vitejs/vite/compare/v7.2.2...
Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), 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 using a curated preset maintained by
. View repository job log here