Repository navigation
chore(deps): Update all patch dependencies - #230
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
renovate
Bot
force-pushed
the
renovate/all-patch-dependencies
branch
from
October 26, 2026 20:37
a1ca0c6 to
a4dc488
Compare
renovate
Bot
force-pushed
the
renovate/all-patch-dependencies
branch
from
October 27, 2026 03:23
a4dc488 to
f77aba2
Compare
renovate
Bot
force-pushed
the
renovate/all-patch-dependencies
branch
24 times, most recently
from
November 2, 2026 17:37
6c222be to
fcf3589
Compare
renovate
Bot
force-pushed
the
renovate/all-patch-dependencies
branch
16 times, most recently
from
November 14, 2026 07:52
468db90 to
a98d3be
Compare
renovate
Bot
force-pushed
the
renovate/all-patch-dependencies
branch
12 times, most recently
from
November 16, 2026 08:51
a7b0347 to
1a712f2
Compare
renovate
Bot
force-pushed
the
renovate/all-patch-dependencies
branch
from
November 16, 2026 20:58
1a712f2 to
79f57fd
Compare
This file contains hidden or 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
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
6.9.7→6.9.81.2.96→1.2.992.29.1→2.29.34.3.3→4.3.50.8.5→0.8.60.8.13→0.8.141.167.2→1.167.33.13.49→3.13.532.8.3→2.8.42.7.2→2.7.32.14.0→2.14.17.0.2005→7.0.20071.9.17→1.9.194.3.3→4.3.58.3.5→8.3.82.11.14→2.11.16Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
generaltranslation/paraglide-js (@inlang/paraglide-js)
v2.29.3Patch Changes
d34c86c: Stop the bundler plugins from rewriting unchanged output when a watch event arrives beforebuildStartor after a failed compile. Such a recompile now starts from the hashes of the output on disk, asbuildStartdoes, so it writes only the files that differ. Previously it rewrote every generated file, and in Vite each rewritten message module became another watch event: withmessage-modulesand a few thousand messages, a dev server could stay busy for minutes after startup.v2.29.2Patch Changes
6146ffd: Emit TypeScript declarations with thetscof TypeScript 7 when it is installed beside TypeScript 5/6 under the@typescript/nativealias, as documented forsvelte-check --tsgo. On largelocale-modulesprojects this is much faster than the compiler API of TypeScript 5/6. The declarations change the way they do when upgradingtypescriptto 7: formatting, ordering and some JSDoc.When
additionalFilescontains JavaScript, keep using the TypeScript 5/6 compiler API to preserve project dependency resolution and inferred types.tailwindlabs/tailwindcss (@tailwindcss/vite)
v4.3.5Compare Source
Fixed
matchVariantplugin with thousands of values) (#20663)color-mix(…)without a color interpolation method (e.g.color-mix(var(--color-red-500))orcolor-mix(currentcolor 50%, transparent)) (#20658, #20666)@tailwindcss/oxide-wasm32-wasiloads instead of hanging forever (e.g. withNAPI_RS_FORCE_WASI=erroror in WebContainers) (#20667)as: '*.css'from the@tailwindcss/turbopacksetup in its README, because it breaks CSS modules (#20660)<!--and-->between top-level rules in CSS instead of throwing or swallowing the next rule (e.g.a { color: red } --> b { color: blue }) (#20665)@tailwindcss/oxide-wasm32-wasidetects changed and new source files after the first scan (e.g. in WebContainers) (#20487)skipLibCheck: falsecaused by imports of unshipped modules in the@tailwindcss/nodetype declarations (#20632)v4.3.4Compare Source
Added
@tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#20367)Fixed
@sourcefiles whose real paths aren't otherwise scanned (#20356)@scopewrap generated utilities instead of nesting inside them (#20369)@scoperules preserve their scoping semantics when flattened (#20369)@scopeby wrapping them in:where(:scope)(#20369)var()fallbacks (e.g.var(--tw-blur,)→var(--tw-blur, )) (#20373)max-[64rem]:flex→max-lg:flex) (#20380)@tailwindcss/vitefrom crashing on every edit under Vite's experimentalbundledDevmode (#20379)@tailwindcss/oxidefalls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasinow installs on all platforms, but only loads when no native binding is available) (#20383)%wand%Wliterals using angle brackets or custom delimiters (e.g.%w<flex>,%w|flex|), including in Slim and Haml templates (#20387)--default(…)values in functional@utilitydefinitions (e.g.--default(box alphabetic)no longer becomesboxalphabetic) (#20392).gitignorefiles (e.g./*followed by!/…patterns) (#20397)theme('…')namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of itsDEFAULTkey (#20399)@tailwindcss/vitefrom forcing full-page reloads for scanned files that Vite does not handle as modules (e.g..phpfiles) (#20414)unset(#20417)rounded-sm/[5],shadow-sm/foo,stroke-2/50) (#20419)and,or, andnotinside selectors insupports-[…]variants (e.g.supports-[selector(a:not(.foo))]:flex) (#20420)::ng-deepand:host-context()when optimizing CSS (#20434)bg-red-500/50/andgroup-hover/foo//bar:flex) (#20466)min-*,max-*, and container query variants with decimal values are sorted numerically (e.g.min-[40.25rem]beforemin-[40.5rem]) (#20512)\*/are closed correctly instead of swallowing the CSS that follows (e.g./* C:\temp\*/) (#20508)group-*andpeer-*variants (#20513)loadModuleandloadStylesheetcallbacks after compilation (#20531)&when moving a pseudo-element into*or**(e.g.[&_::before]:flex→**:[&::before]:flex) (#20550)Set.prototype.intersectionpolyfill incanonicalizeCandidates(…)returns the intersection instead of the first set on Node.js < 22 (#20562)theme(…)alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g.theme(colors.red.500/.12345)→text-red-500/[12.345%], nottext-red-500/[12.345]) (#20563)theme(…)alphas as an arbitrary percentage when a custom--opacity-*theme value would change the opacity (e.g.theme(colors.red.500/50%)→text-red-500/[50%]with--opacity-50: 10%) (#20563)@propertyfallback isn't applied in Safari versions that no longer supportmargin-trim: inline(#20569)dvminandsviand font-relative units likecapandrexas lengths in arbitrary values (e.g.text-[10dvmin]generatesfont-sizeinstead ofcolor) (#20516)tailwindcss canonicalizeso they don't end up in the results on stdout (#20561)input(pattern=/"/.source)) (#20547, #20572)--value(…)warnings (#20554)text-foreground text-primary→text-primary, nottext-card-checked-border) (#20540)mt-card mb-card→my-card, notmy-4) (#20574)@tailwindcss/postcssrewrites relativeurl(…)s of stylesheets that are inlined before it runs (e.g.@imports in Vite) in optimized builds (#20576)selection:*on a utility with a nested& > *rule) (#20575)w-[calc(1px]or[--x:a[b]) (#20577)collapse: truefrom taking exponentially longer when classes are linked through a utility that sets many properties (e.g.sr-only) (#20558)&is substituted inside:-moz-any(…)and:-webkit-any(…)in custom variants (e.g.@custom-variant firefox (:-moz-any(&));) (#20486)@tailwindcss/turbopackand@tailwindcss/webpackrebuild when the input CSS changes (e.g.next devwith Turbopack no longer serves the CSS of the previous edit) (#20582)--tw-*variable when an unrelated property has the same value (e.g.link mt-4no longer becomesmt-4whenlinksetsmargin-top: 16pxand--tw-translate-x: 16px) (#20593)@utilitynames as the CSS spec does (e.g.@theme { --color-\0: red; }no longer registers--color-0) (#20591)!importantinside strings, comments orurl()in declaration values as the important flag (e.g.content: "a !important b") (#20627);(e.g.--foo: baras the last declaration) (#20653);at the end of the CSS input (e.g.color: red) (#20655)TanStack/devtools (@tanstack/devtools-vite)
v0.8.6Compare Source
Patch Changes
#539
ed8b314- Source injection no longer stops after the dev server parses a regex literal. Before this fix, a regex literal cachedvalueas a child key ofLiteralnodes. Every later file with a string literal then threw during the walk and got zerodata-tsd-sourceattributes.#540
012421f- Stop the console pipe feedback loop with Vite 8server.forwardConsole. The server side of the pipe no longer sends browser logs that Vite printed in the terminal back to the browser.#548
40f32e4- Run source injection before the transforms of other plugins (unless they also useorder: 'pre'), also whendevtools()is not first in the plugins array. Before this fix, a framework plugin that changed the code of only one environment shifted the line numbers, sodata-tsd-sourcediffered between SSR and client and caused hydration warnings.#541
df1464c- Fix "Go to Source" for files outside the current working directory, for example a package in a monorepo or Vite run from another directory. The editor got a path with the working directory added twice. Also answer a missing or malformedsourcewith400instead of leaving the request pending.#542
9c58288- Remove theintentbin from the published packages. It took overnode_modules/.bin/intentfrom@tanstack/intentand imported the removed@tanstack/intent/intent-librarysubpath. The packages now have thetanstack-intentkeyword, which current@tanstack/intentuses to find their skills.#545
d018c4c- Reject event bus requests to install a package when the name is not a valid npm package name. On macOS and Linux, run the package manager without a shell. Also reject a plugin import name that is not a JavaScript identifier, because it is written into your source file as code.#538
7cb0a8d- Inject the event bus port, host, and protocol into Vite pre-bundled dependency chunks too. Before this fix, a client installed from npm kept the default port 4206 and could not connect when the server bus used another port.Updated dependencies [
ed8b314,012421f,df1464c,d018c4c]:TanStack/devtools (@tanstack/solid-devtools)
v0.8.14Patch Changes
#543
bbe529a- Require solid-js 1.9.13 or later. Our compiled output importsusefromsolid-js/web, and the server build of solid-js 1.9.12 and earlier does not export it. Before this fix, SSR apps with an older solid-js in their lockfile could not start the dev server.#557
f4ca00c- Cap thesolid-jspeer range at^1. The previous open-ended>=range would accept Solid 2.0.0 once it is released, but these packages are built against Solid 1 and do not work with Solid 2.Updated dependencies [
8b3a032,f315fe8,7b5f1ee,9c58288,bbe529a,f4ca00c]:TanStack/router (@tanstack/solid-router-devtools)
v1.167.3Compare Source
Patch Changes
bbf9b75]:TanStack/virtual (@tanstack/solid-virtual)
v3.13.53Compare Source
Patch Changes
acaef5e,bd08fe5]:v3.13.52Compare Source
Patch Changes
9d7ff67]:v3.13.51Compare Source
Patch Changes
35ad56d,979c1b4]:v3.13.50Compare Source
Patch Changes
2343004]:tauri-apps/plugins-workspace (@tauri-apps/plugin-dialog)
v2.8.4Compare Source
vitejs/vite (vite)
v8.3.8Compare Source
Bug Fixes
magicStringandastin transform hook meta (#24012) (a3b28e8)build.cssCodeSplit: false(#23112) (e4ad62b)yarn config geton Windows (#24013) (3f6c4cd)Performance Improvements
net useuntil a UNC path is resolved on Windows (#24014) (b643046)Miscellaneous Chores
magicStringandastin transform hook meta (#24012)" (#24065) (afc44f0)Code Refactoring
Tests
v8.3.7Compare Source
Bug Fixes
Miscellaneous Chores
Tests
onTestFinishedfor tear downs (#24003) (a579e35)Build System
v8.3.6Compare Source
Bug Fixes
@rollup/plugin-aliasto v6.0.1 (#23862) (67c965b)server.forwardConsole(#23933) (4f340fd)build.sourcemapfrom environment (#23879) (82e7aa0)$patterns in static alias replacements (#23703) (1b6ed05)ssr.target=webworker(#23759) (a711f1c)inputfor SSR build whenbuild.ssr: true(#23898) (90bc034).wasmoutsideserver.fs(#23914) (64e2467)new URL(..., import.meta.url)(#23780) (e954a9c)Performance Improvements
cssScopeTo(#23889) (1b905e5)Miscellaneous Chores
Build System
solidjs/solid-vite-plugin (vite-plugin-solid)
v2.11.16Compare Source
Patch Changes
1ea0fba: Load the client build of solid-js in test files that set// @vitest-environment nodewhentest.environmentisjsdomorhappy-dom. Thessrenvironment keeps thebrowsercondition again, and only the conditions Vitest passes to Node leave it out, somsw/nodestill loads.v2.11.15Compare Source
Patch Changes
62e2b75: Production builds now dedupesolid-jsthe same way dev does. A dependency with its own nested copy ofsolid-jsno longer adds a second runtime to the bundle, which broke context lookups (#112).a732eeb: Avoid overriding environments configured in Vitest workspaces and projects with thejsdomdefault9e67618: fix: exclude test mode from HMR setupa7ec25f: FixTypeError: Cannot read properties of undefined (reading 'extend')in tests on Vitest before 1.0 with@testing-library/jest-dom6 or later installed (#141). The plugin now injects jest-dom's ESMvitestentry as an absolute path for those Vitest versions, because they load the CommonJS entry from a bare specifier.6cc30fe: Only inject the@testing-library/jest-domVitest setup file when the package resolves from the project root. Previously the check ran from the plugin's own location, so with pnpm a transitive jest-dom (for example via Storybook) made Vitest fail withFailed to load url .../@testing-library/jest-dom/vitest.d0e47f1: Vitest runs keep thejsdomenvironment and the@testing-library/jest-domsetup file whentest.server.deps.externalalready listssolid-js. The plugin used to drop its wholetestconfig in that case.f8439e8: The plugin no longer changesresolve.alias. An alias object in your config now keeps priority over aliases that later plugins add, such asvite-plugin-node-polyfillsmappingpath(#130).df3ba8a: Compile modules whose id has the extension after the query, such as unplugin-icons'~icons/mdi/folder?width=2em.tsx. Since 2.11.2 these were left to Vite's default JSX transform, which produced React code (#206). Customextensionsare now also matched when the query contains a dot.b50c064: Keep$ServerOnlytemplates in client transforms while HMR is active so hot updates of components using$ServerOnlyno longer throwtemplate is not a function. An explicitsolid.omitServerOnlyTemplatessetting still takes precedence.cd79ed9: Withoutssr: true, modules loaded on the server now compile to non-hydratable SSR output instead of DOM output. Prerendering a client-rendered app withssrLoadModuleno longer throws "Client-only API called on the server side" (#64). Vitest keeps DOM output.9c17655: Server builds withssr.target: 'webworker'now resolve the server build ofsolid-js. The plugin adds theworkerexport condition to that build, sorenderToStringand the other server APIs no longer resolve to their browser stubs (#153). This works on Vite 4 and later.8909380: Vite 8's dependency scan no longer breaks on.tsxfiles (issue #262).The plugin previously set
optimizeDeps.rolldownOptions.transform.jsx: 'preserve'to stop Rolldown from injectingreact/jsx-dev-runtimeimports during the scan — but the scanner re-parses the transformed
output as plain JS (
import.meta.globhandling force-tags modules asjs), so any.tsxwith JSX was a hardPARSE_ERROR: Unexpected JSX expressionthat aborted the whole scan and skipped pre-bundling. Thescan transform now uses the classic JSX runtime, which lowers JSX to bare
React.createElementcalls without injecting any import: the scan outputis never executed, it only exists so rolldown can walk the import graph,
so the undefined identifier is harmless. Backport of the fix already on
the 3.0.0-next line.
5d6846c: When the root config declarestest.projectsand leavestest.sharedViteServerunset, the plugin now sets it tofalseso every inline project resolves its own Vite config, as under Vitest 4. An explicit value is respected. Vitest 5 defaults the option totrue, and a shared inline project takes itstestoptions from the raw root block captured before anyconfighook runs, so it lost everything the plugin injects (thejsdomdefault, the@testing-library/jest-domsetup file,server.deps). Ports #370; refs #369.32adc90: In Vitest DOM tests (the jsdom defauConfiguration
📅 Schedule: (in timezone Europe/Oslo)
🚦 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.