chore(deps): update devdependencies-major (major) by renovate[bot] · Pull Request #158 · technologiestiftung/fairgnuegen

renovate · 2025-02-24T04:26:23Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@babel/plugin-transform-unicode-property-regex (source)	`7.27.1` → `8.0.1`
@react-router/dev (source)	`7.1.5` → `8.3.0`
@types/node (source)	`22.13.1` → `24.13.3`
@vitejs/plugin-legacy (source)	`6.1.1` → `8.2.3`
@vitejs/plugin-react (source)	`4.3.4` → `6.1.0`
eslint (source)	`9.20.0` → `10.9.0`
eslint-plugin-react-hooks (source)	`5.1.0` → `7.1.1`
globals	`15.14.0` → `17.11.0`
tailwindcss (source)	`3.4.17` → `4.3.3`
typescript (source)	`5.7.3` → `7.0.2`
vite-tsconfig-paths	`5.1.4` → `6.1.1`

Release Notes

babel/babel (@babel/plugin-transform-unicode-property-regex)

`v8.0.1`

Compare Source

💥 Breaking Change

babel-core, babel-plugin-transform-object-rest-spread, babel-plugin-transform-runtime, babel-preset-env, babel-standalone
- #18079 Actually remove preset-env's useBuiltIns (@nicolo-ribaudo)

`v8.0.0`

Compare Source

👓 Spec Compliance

babel-core
- #18039 perf: Only extract source map comments at the end of the file (@liuxingbaoyu)

💥 Breaking Change

babel-cli, babel-node, babel-plugin-proposal-decorators, babel-plugin-transform-classes, babel-plugin-transform-function-name, babel-plugin-transform-modules-commonjs, babel-plugin-transform-object-rest-spread, babel-plugin-transform-parameters, babel-plugin-transform-react-constant-elements, babel-plugin-transform-regenerator, babel-preset-env, babel-register
- #18069 Fallback to assuming ESM support with modules: auto (@nicolo-ribaudo)
babel-plugin-transform-runtime, babel-runtime-corejs3, babel-runtime
- #18036 Remove corejs exports for @babe/runtime-corejs3 (@liuxingbaoyu)
babel-parser
- #18034 Remove locations: "packed" (@liuxingbaoyu)

🐛 Bug Fix

babel-generator
- #18046 fix(generator): improve new callee parens check (@JLHwung)
babel-plugin-transform-modules-systemjs
- #18032 fix(systemjs): support proto as an export name (@JLHwung)

📝 Documentation

#18070 Add EOL date for Babel 7 (end of June 2027) to SECURITY.md (@nicolo-ribaudo)

🏠 Internal

#18018 ci: enforce yarn integrity (@JLHwung)

🏃‍♀️ Performance

babel-core
- #18039 perf: Only extract source map comments at the end of the file (@liuxingbaoyu)

`v7.29.7`

Compare Source

v7.29.7 (2026-05-25)

Re-release all packages with npm provenance attestations

`v7.28.6`

Compare Source

v7.28.6 (2026-01-12)

Thanks @kadhirash and @kolvian for your first PRs!

🐛 Bug Fix

babel-cli, babel-code-frame, babel-core, babel-helper-check-duplicate-nodes, babel-helper-fixtures, babel-helper-plugin-utils, babel-node, babel-plugin-transform-flow-comments, babel-plugin-transform-modules-commonjs, babel-plugin-transform-property-mutators, babel-preset-env, babel-traverse, babel-types
- #17589 Improve Unicode handling in code-frame tokenizer (@JLHwung)
babel-plugin-transform-regenerator
- #17556 fix: transform-regenerator correctly handles scope (@liuxingbaoyu)
babel-plugin-transform-react-jsx
- #17538 fix: Keep jsx comments (@liuxingbaoyu)

💅 Polish

babel-core, babel-standalone
- #17606 Polish(standalone): improve message on invalid preset/plugin (@JLHwung)

🏠 Internal

babel-plugin-bugfix-v8-static-class-fields-redefine-readonly, babel-plugin-proposal-decorators, babel-plugin-proposal-import-attributes-to-assertions, babel-plugin-proposal-import-wasm-source, babel-plugin-syntax-async-do-expressions, babel-plugin-syntax-decorators, babel-plugin-syntax-destructuring-private, babel-plugin-syntax-do-expressions, babel-plugin-syntax-explicit-resource-management, babel-plugin-syntax-export-default-from, babel-plugin-syntax-flow, babel-plugin-syntax-function-bind, babel-plugin-syntax-function-sent, babel-plugin-syntax-import-assertions, babel-plugin-syntax-import-attributes, babel-plugin-syntax-import-defer, babel-plugin-syntax-import-source, babel-plugin-syntax-jsx, babel-plugin-syntax-module-blocks, babel-plugin-syntax-optional-chaining-assign, babel-plugin-syntax-partial-application, babel-plugin-syntax-pipeline-operator, babel-plugin-syntax-throw-expressions, babel-plugin-syntax-typescript, babel-plugin-transform-async-generator-functions, babel-plugin-transform-async-to-generator, babel-plugin-transform-class-properties, babel-plugin-transform-class-static-block, babel-plugin-transform-dotall-regex, babel-plugin-transform-duplicate-named-capturing-groups-regex, babel-plugin-transform-explicit-resource-management, babel-plugin-transform-exponentiation-operator, babel-plugin-transform-json-strings, babel-plugin-transform-logical-assignment-operators, babel-plugin-transform-nullish-coalescing-operator, babel-plugin-transform-numeric-separator, babel-plugin-transform-object-rest-spread, babel-plugin-transform-optional-catch-binding, babel-plugin-transform-optional-chaining, babel-plugin-transform-private-methods, babel-plugin-transform-private-property-in-object, babel-plugin-transform-regexp-modifiers, babel-plugin-transform-unicode-property-regex, babel-plugin-transform-unicode-sets-regex
- #17580 Allow Babel 8 in compatible Babel 7 plugins (@nicolo-ribaudo)

🏃‍♀️ Performance

babel-plugin-transform-react-jsx
- #17555 perf: Use lighter traversal for jsx __source,__self (@liuxingbaoyu)

Committers: 7

Babel Bot (@babel-bot)
Eliot Pontarelli (@kolvian)
Huáng Jùnliàng (@JLHwung)
Kadhirash Sivakumar (@kadhirash)
Nicolò Ribaudo (@nicolo-ribaudo)
@liuxingbaoyu
coderaiser (@coderaiser)

remix-run/react-router (@react-router/dev)

`v8.3.0`

Compare Source

Minor Changes

Restart react-router dev with --conditions=development when not already configured (#15291)

Patch Changes

Allow typescript@7 to be used (#15317)

Unstable Changes

⚠️ Unstable features are not recommended for production use

Add unstable_rsc/client-version client build version virtual module (#15318)
Support the subResourceIntegrity config option in RSC Framework Mode (#15321)

Migration guide

No changes are required when using the default RSC SSR entry. If you maintain a custom app/entry.ssr.tsx, import the new virtual module and pass its hashes to React's importMap render option:

+import subResourceIntegrity from "virtual:react-router/unstable_rsc/subresource-integrity";

return renderToReadableStream(<RSCStaticRouter getPayload={getPayload} />, {
  ...options,
  bootstrapScriptContent,
  formState,
+ importMap: subResourceIntegrity
+   ? { integrity: subResourceIntegrity }
+   : undefined,
  signal: request.signal,
});

Updated dependencies:

`v8.2.0`

Compare Source

Minor Changes

Add a Web Streams default server entry for non-Node Framework mode apps (#15290)
- Apps using @react-router/node, @react-router/express, or @react-router/serve continue to use the renderToPipeableStream default server entry
- Apps without those Node server adapter dependencies use a renderToReadableStream default server entry
- Non-Node apps with their own entry.server.tsx may be able to remove it in favor of the default if it is not doing anything custom
Detect nub as a supported package manager when installing framework dependencies (#15276)

Patch Changes

Detect user rolldownOptions config in Vite 8+ (#15278)

Unstable Changes

⚠️ Unstable features are not recommended for production use

Add the future.unstable_enableNodeReadableStream flag to opt Node Framework mode apps into using renderToReadableStream instead of renderToPipeableStream (#15290)
- This flag has no effect if you have your own entry.server.tsx
Updated dependencies:

`v8.1.0`

Compare Source

Patch Changes

Fix a regression with the new prerendering plugin where the react-router.config.ts buildEnd hook would run before prerendering was completed (#15211)
Fixed react-router typegen crashes under the Bun runtime when Babel default imports are already unwrapped (#15214)
Replace the deprecated envFile:false Vite config with envDir:false to eliminate a deprecation warning when using vite@8.1.0+ (#15230)
Only add the "node" Vite server condition for Framework mode apps that declare a Node server adapter dependency (#15242)
- This prevents non-Node SSR runtimes from resolving Node-specific package exports by default
Updated dependencies:

Major Changes

Remove @react-router/dev/vite/cloudflare dev proxy export; use @cloudflare/vite-plugin instead (#15077)
- Drops support for wrangler@3 as a peer dependency of @react-router/dev
Remove the future.v8_trailingSlashAwareDataRequests flag (#15100)
- Trailing slash-aware data request URLs are now the default behavior.
Remove future.v8_passThroughRequests flag - the raw incoming request is now always passed through to loader/action. (#15079)
Move future.v8_splitRouteModules to a top-level splitRouteModules config option and change the default behavior to true (#15086)
- Set splitRouteModules: false to keep route modules in a single chunk
- Set splitRouteModules: "enforce" to require all routes to be splittable
Update minimum Node version to 22.22.0 (#14928)
Require Vite 7+ and make the Vite Environment API build path mandatory (#15077)
Removed the future.v8_viteEnvironmentApi flag because the Vite Environment API is always enabled (#15077)
Removed the future.unstable_previewServerPrerendering flag and make prerendering with the Vite Environment API the default. (#15077)

Minor Changes

Bump dependencies (#15080)
- Bumped @babel/core from ^7.27.7 to ^7.29.7
- Bumped @babel/generator from ^7.27.5 to ^7.29.7
- Bumped @babel/parser from ^7.27.7 to ^7.29.7
- Bumped @babel/plugin-syntax-jsx from ^7.27.1 to ^7.29.7
- Bumped @babel/preset-typescript from ^7.27.1 to ^7.29.7
- Bumped @babel/traverse from ^7.27.7 to ^7.29.7
- Bumped @babel/types from ^7.27.7 to ^7.29.7
- Bumped dedent from ^1.5.3 to ^1.7.2
- Bumped jsesc from 3.0.2 to 3.1.0
- Bumped lodash from ^4.17.21 to ^4.18.1
- Bumped prettier from ^3.6.2 to ^3.8.3
- Bumped @remix-run/node-fetch-server from ^0.13.0 to ^0.13.3
- Bumped react-refresh from ^0.14.0 to ^0.18.0
- Bumped semver from ^7.3.7 to ^7.8.1
- Bumped tinyglobby from ^0.2.14 to ^0.2.16
- Bumped valibot from ^1.2.0 to ^1.4.1
Replace cookie and set-cookie-parser with cookie-es (#15109)
Removed the vite-node dependency in favor of Vite's native module runner APIs (#15104)

Patch Changes

Bump dependencies (#15080)
- Bumped @babel/core from ^7.29.0 to ^7.29.7
- Bumped @babel/generator from ^7.29.1 to ^7.29.7
- Bumped @babel/parser from ^7.29.3 to ^7.29.7
- Bumped @babel/plugin-syntax-jsx from ^7.28.6 to ^7.29.7
- Bumped @babel/preset-typescript from ^7.28.5 to ^7.29.7
- Bumped @babel/traverse from ^7.29.0 to ^7.29.7
- Bumped @babel/types from ^7.29.0 to ^7.29.7
- Bumped babel-dead-code-elimination from ^1.0.6 to ^1.0.12
- Bumped chokidar from ^4.0.0 to ^5.0.0
- Bumped es-module-lexer from ^1.3.1 to ^2.1.0
- Bumped exit-hook from 2.2.1 to 5.1.0
- Bumped isbot from ^5.1.11 to ^5.1.40
- Bumped p-map from ^7.0.3 to ^7.0.4
- Bumped pathe from ^1.1.2 to ^2.0.3
- Bumped pkg-types from ^2.3.0 to ^2.3.1
- Bumped react-refresh from ^0.14.0 to ^0.18.0
- Bumped semver from ^7.8.0 to ^7.8.1
- Bumped tinyglobby from ^0.2.14 to ^0.2.16
- Bumped valibot from ^1.4.0 to ^1.4.1
Fix Windows libuv assertion (!(handle->flags & UV_HANDLE_CLOSING) in src/win/async.c) during prerendering by using node:http instead of fetch for internal prerender requests against the Vite preview server (#15077)
Updated dependencies:

`v7.18.3`

Compare Source

`v7.18.2`

Compare Source

`v7.18.1`

Compare Source

`v7.18.0`

Compare Source

Patch Changes

Pass Vite server.watch config to child compiler in development mode. (#15178)
Ignore external Vite server environments in Framework Mode build hooks (#14883)

When future.v8_viteEnvironmentApi is enabled, React Router previously treated any non-client Vite environment as its own server build. This caused issues with integrations like Nitro, where plugins can register additional environments.

Framework Mode build hooks now ignore external server environments and only process the app's own server build.
Updated dependencies:

`v7.17.0`

Compare Source

Patch Changes

Fix future flag warning URLs and only log each future flag warning one time (#15138)

Unstable Changes

⚠️ Unstable features are not recommended for production use

Prevent RSC route module server exports from being scanned by the client dependency optimizer when future.unstable_optimizeDeps is enabled. (#15005)
Updated dependencies:

`v7.16.0`

Compare Source

Minor Changes

Stabilize future.unstable_trailingSlashAwareDataRequests as future.v8_trailingSlashAwareDataRequests (#15098)
- The unstable flag is no longer supported and will error during config resolution
Log future flag warnings for upcoming React Router v8 flags (#15029)
- v8_middleware, v8_splitRouteModules, v8_viteEnvironmentApi, v8_passThroughRequests, v8_trailingSlashAwareDataRequests

Patch Changes

Updated dependencies:

`v7.15.1`

Compare Source

Patch Changes

Fix basename conflicting with app directory name when Vite base is set (#15027)

When the Vite base config and React Router basename both match the
app directory name (e.g. base: "/app/", basename: "/app/"), Vite would
strip the base prefix from server-build virtual module import paths, causing
"Failed to load url /root.tsx" errors. The fix uses /@fs/ absolute paths
for those imports to bypass Vite's base-stripping logic.
Updated dependencies:

`v7.15.0`

Compare Source

Minor Changes

Stabilize future.unstable_passThroughRequests as future.v8_passThroughRequests (a993f09)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
Stabilize prerender.unstable_concurrency as prerender.concurrency (a993f09)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly
Stabilize future.unstable_subResourceIntegrity as a top-level subResourceIntegrity config option in react-router.config.ts (a993f09)
- ⚠️ This is a breaking change if you have already opted into the unstable version - you will need to update your code accordingly

Patch Changes

Updated dependencies:

`v7.14.2`

Compare Source

Patch Changes

Fix typegen for layouts without pages ([aabf4a1)

Previously, typegen could produce pages: ; in .react-router/types/+routes.ts when a route corresponded to 0 pages.
Now, pages: never; is correctly generated for those cases.

Unstable Changes

⚠️ Unstable features are not recommended for production use

For unstable_reactRouterRSC Vite plugin consumers, require @vitejs/plugin-react in user Vite config, and more reliably split route modules. (#14965) ([aabf4a1)
- ⚠️ This is a breaking change if you have begun using the unstable_reactRouterRSC Vite plugin - please install @vitejs/plugin-react and add the react plugin to your Vite plugins array.
Updated dependencies:

`v7.14.1`

Compare Source

Patch Changes

Add TypeScript 6 support to peer dependency ranges
Updated dependencies:

`v7.14.0`

Compare Source

Minor Changes

Add support for Vite 8 (#14876)

Patch Changes

support for prerendering multiple server bundles with v8_viteEnvironmentApi (#14921)
rsc framework mode prerender / spa mode support (#14907)
UNSTABLE RSC FRAMEWORK MODE BREAKING CHANGE - Existing route module exports remain unchanged from stable v7 non-RSC mode, but new exports are added for RSC mode. If you want to use RSC features, you will need to update your route modules to export the new annotations. (#14901)

If you are using RSC framework mode currently, you will need to update your route modules to the new conventions. The following route module components have their own mutually exclusive server component counterparts:

Server Component Export Client Component

ServerComponent default

ServerErrorBoundary ErrorBoundary

ServerLayout Layout

ServerHydrateFallback HydrateFallback

If you were previously exporting a ServerComponent, your ErrorBoundary, Layout, and HydrateFallback were also server components. If you want to keep those as server components, you can rename them and prefix them with Server. If you were previously importing the implementations of those components from a client module, you can simply inline them.

Example:

Before
```
import { ErrorBoundary as ClientErrorBoundary } from "./client";

export function ServerComponent() {
  // ...
}

export function ErrorBoundary() {
  return <ClientErrorBoundary />;
}

export function Layout() {
  // ...
}

export function HydrateFallback() {
  // ...
}
```
After
```
export function ServerComponent() {
  // ...
}

export function ErrorBoundary() {
  // previous implementation of ClientErrorBoundary, this is now a client component
}

export function ServerLayout() {
  // rename previous Layout export to ServerLayout to make it a server component
}

export function ServerHydrateFallback() {
  // rename previous HydrateFallback export to ServerHydrateFallback to make it a server component
}
```
update the reveal command to support rsc for entry.client, entry.rsc, entry.ssr (#14904)
Updated dependencies:
- react-router@7.14.0
- @react-router/node@7.14.0
- @react-router/serve@7.14.0

`v7.13.2`

Compare Source

Patch Changes

Fix react-router dev crash when Unix socket files exist in the project root (#14854)
Escape redirect locations in prerendered redirect HTML (#14880)

Add future.unstable_passThroughRequests flag (#14775)

By default, React Router normalizes the request.url passed to your loader, action, and middleware functions by removing React Router's internal implementation details (.data suffixes, index + _routes query params).

Enabling this flag removes that normalization and passes the raw HTTP request instance to your handlers. This provides a few benefits:

Reduces server-side overhead by eliminating multiple new Request() calls on the critical path
Allows you to distinguish document from data requests in your handlers base don the presence of a .data suffix (useful for observability purposes)

If you were previously relying on the normalization of request.url, you can switch to use the new sibling unstable_url parameter which contains a URL instance representing the normalized location:

// ❌ Before: you could assume there was no `.data` suffix in `request.url`
export async function loader({ request }: Route.LoaderArgs) {
  let url = new URL(request.url);
  if (url.pathname === "/path") {
    // This check will fail with the flag enabled because the `.data` suffix will
    // exist on data requests
  }
}

// ✅ After: use `unstable_url` for normalized routing logic and `request.url`
// for raw routing logic
export async function loader({ request, unstable_url }: Route.LoaderArgs) {
  if (unstable_url.pathname === "/path") {
    // This will always have the `.data` suffix stripped
  }

  // And now you can distinguish between document versus data requests
  let isDataRequest = new URL(request.url).pathname.endsWith(".data");
}

Add a new unstable_url: URL parameter to route handler methods (loader, action, middleware, etc.) representing the normalized URL the application is navigating to or fetching, with React Router implementation details removed (.datasuffix, index/_routes query params) (#14775)

This is being added alongside the new future.unstable_passthroughRequests future flag so that users still have a way to access the normalized URL when that flag is enabled and non-normalized request's are being passed to your handlers. When adopting this flag, you will only need to start leveraging this new parameter if you are relying on the normalization of request.url in your application code.

If you don't have the flag enabled, then unstable_url will match request.url.
Updated dependencies:
- react-router@7.13.2
- @react-router/node@7.13.2
- @react-router/serve@7.13.2

`v7.13.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.13.1
- @react-router/node@7.13.1
- @react-router/serve@7.13.1

`v7.13.0`

Compare Source

Patch Changes

Bump @remix-run/node-fetch-server dep (#14704)
Updated dependencies:
- react-router@7.13.0
- @react-router/node@7.13.0
- @react-router/serve@7.13.0

`v7.12.0`

Compare Source

Minor Changes

Add additional layer of CSRF protection by rejecting submissions to UI routes from external origins. If you need to permit access to specific external origins, you can specify them in the react-router.config.ts config allowedActionOrigins field. (#14708)

Patch Changes

Fix Maximum call stack size exceeded errors when HMR is triggered against code with cyclic imports (#14522)
fix(vite): Skip SSR middleware in preview server for SPA mode (#14673)
[UNSTABLE] Add a new future.unstable_trailingSlashAwareDataRequests flag to provide consistent behavior of request.pathname inside middleware, loader, and action functions on document and data requests when a trailing slash is present in the browser URL. (#14644)

Currently, your HTTP and request pathnames would be as follows for /a/b/c and /a/b/c/

URL /a/b/c HTTP pathname request pathname`

Document /a/b/c /a/b/c ✅

Data /a/b/c.data /a/b/c ✅

URL /a/b/c/ HTTP pathname request pathname`

Document /a/b/c/ /a/b/c/ ✅

Data /a/b/c.data /a/b/c ⚠️

With this flag enabled, these pathnames will be made consistent though a new _.data format for client-side .data requests:

URL /a/b/c HTTP pathname request pathname`

Document /a/b/c /a/b/c ✅

Data /a/b/c.data /a/b/c ✅

URL /a/b/c/ HTTP pathname request pathname`

Document /a/b/c/ /a/b/c/ ✅

Data /a/b/c/_.data ⬅️ /a/b/c/ ✅

This a bug fix but we are putting it behind an opt-in flag because it has the potential to be a "breaking bug fix" if you are relying on the URL format for any other application or caching logic.

Enabling this flag also changes the format of client side .data requests from /_root.data to /_.data when navigating to / to align with the new format. This does not impact the request pathname which is still / in all cases.
Updated dependencies:
- react-router@7.12.0
- @react-router/node@7.12.0
- @react-router/serve@7.12.0

`v7.11.0`

Compare Source

Minor Changes

feat: add vite preview support (#14507)

Patch Changes

rsc framework mode manual chunking for react and react-router deps (#14655)
add support for throwing redirect Response's at RSC render time (#14596)
support custom entrypoints for RSC framework mode (#14643)
routeRSCServerRequest replace fetchServer with serverResponse (#14597)
rsc framewlrk mode - optimize react-server-dom-webpack if in project package.json (#14656)
Updated dependencies:
- react-router@7.11.0
- @react-router/serve@7.11.0
- @react-router/node@7.11.0

`v7.10.1`

Compare Source

Patch Changes

Import ESM package pkg-types with a dynamic import() to fix issues on Node 20.18 (#14624)
Update valibot dependency to ^1.2.0 to address GHSA-vqpr-j7v3-hqw9 (#14608)
Updated dependencies:
- react-router@7.10.1
- @react-router/node@7.10.1
- @react-router/serve@7.10.1

`v7.10.0`

Compare Source

Minor Changes

Stabilize future.v8_splitRouteModules, replacing future.unstable_splitRouteModules (#14595)
- ⚠️ This is a breaking change if you have begun using future.unstable_splitRouteModules. Please update your react-router.config.ts.
Stabilize future.v8_viteEnvironmentApi, replacing future.unstable_viteEnvironmentApi (#14595)
- ⚠️ This is a breaking change if you have begun using future.unstable_viteEnvironmentApi. Please update your react-router.config.ts.

Patch Changes

Load environment variables before evaluating routes.ts (#14446)

For example, you can now compute your routes based on VITE_-prefixed environment variables:

# .env
VITE_ENV_ROUTE=my-route

// app/routes.ts
import { type RouteConfig, route } from "@react-router/dev/routes";

const routes: RouteConfig = [];
if (import.meta.env.VITE_ENV_ROUTE === "my-route") {
  routes.push(route("my-route", "routes/my-route.tsx"));
}

export default routes;

Updated dependencies:
- react-router@7.10.0
- @react-router/node@7.10.0
- @react-router/serve@7.10.0

`v7.9.6`

Compare Source

Patch Changes

Use a dynamic import() to load ESM-only p-map dependency to avoid issues on Node 20.18 and below (#14492)
Short circuit HEAD document requests before calling renderToPipeableStream in the default entry.server.tsx to more closely align with the spec (#14488)
Updated dependencies:
- react-router@7.9.6
- @react-router/node@7.9.6
- @react-router/serve@7.9.6

`v7.9.5`

Compare Source

Patch Changes

Introduce a prerender.unstable_concurrency option, to support running the prerendering concurrently, potentially speeding up the build. (#14380)
Move RSCHydratedRouter and utils to /dom export. (#14457)
Ensure route navigation doesn't remove CSS link elements used by dynamic imports (#14463)
Typegen: only register route module types for routes within the app directory (#14439)
Updated dependencies:
- react-router@7.9.5
- @react-router/node@7.9.5
- @react-router/serve@7.9.5

`v7.9.4`

Compare Source

Patch Changes

Update valibot dependency to ^1.1.0 (#14379)

New (unstable) useRoute hook for accessing data from specific routes (#14407)

For example, let's say you have an admin route somewhere in your app and you want any child routes of admin to all have access to the loaderData and actionData from admin.

// app/routes/admin.tsx
import { Outlet } from "react-router";

export const loader = () => ({ message: "Hello, loader!" });

export const action = () => ({ count: 1 });

export default function Component() {
  return (
    <div>
      {/* ... */}
      <Outlet />
      {/* ... */}
    </div>
  );
}

You might even want to create a reusable widget that all of the routes nested under admin could use:

import { unstable_useRoute as useRoute } from "react-router";

export function AdminWidget() {
  // How to get `message` and `count` from `admin` route?
}

In framework mode, useRoute knows all your app's routes and gives you TS errors when invalid route IDs are passed in:

export function AdminWidget() {
  const admin = useRoute("routes/dmin");
  //                      ^^^^^^^^^^^
}

useRoute returns undefined if the route is not part of the current page:

export function AdminWidget() {
  const admin = useRoute("routes/admin");
  if (!admin) {
    throw new Error(`AdminWidget used outside of "routes/admin"`);
  }
}

Note: the root route is the exception since it is guaranteed to be part of the current page.
As a result, useRoute never returns undefined for root.

loaderData and actionData are marked as optional since they could be accessed before the action is triggered or after the loader threw an error:

export function AdminWidget() {
  const admin = useRoute("routes/admin");
  if (!admin) {
    throw new Error(`AdminWidget used outside of "routes/admin"`);
  }
  const { loaderData, actionData } = admin;
  console.log(loaderData);
  //          ^? { message: string } | undefined
  console.log(actionData);
  //          ^? { count: number } | undefined
}

If instead of a specific route, you wanted access to the current route's loaderData and actionData, you can call useRoute without arguments:

export function AdminWidget() {
  const currentRoute = useRoute();
  currentRoute.loaderData;
  currentRoute.actionData;
}

This usage is equivalent to calling useLoaderData and useActionData, but consolidates all route data access into one hook: useRoute.

Note: when calling useRoute() (without a route ID), TS has no way to know which route is the current route.
As a result, loaderData and actionData are typed as unknown.
If you want more type-safety, you can either narrow the type yourself with something like zod or you can refactor your app to pass down typed props to your AdminWidget:

export function AdminWidget({
  message,
  count,
}: {
  message: string;
  count: number;
}) {
  /* ... */
}

Updated dependencies:
- react-router@7.9.4
- @react-router/node@7.9.4
- @react-router/serve@7.9.4

`v7.9.3`

Compare Source

Patch Changes

Updated dependencies:
- react-router@7.9.3
- @react-router/node@7.9.3
- @react-router/serve@7.9.3

`v7.9.2`

Compare Source

Patch Changes

Fix preset future flags being ignored during config resolution (#14369)

Fixes a bug where future flags defined by presets were completely ignored. The config resolution was incorrectly reading from reactRouterUserConfig.future instead of the merged userAndPresetConfigs.future, causing all preset-defined future flags to be lost.

This fix ensures presets can properly enable experimental features as intended by the preset system design.
Add unstable support for RSC Framework Mode (#14336)
Switch internal vite plugin Response logic to use @remix-run/node-fetch-server (#13927)
Updated dependencies:
- react-router@7.9.2
- @react-router/serve@7.9.2
- @react-router/node@7.9.2

`v7.9.1`

Compare Source

Patch Changes

Fix internal Future interface naming from middleware -> v8_middleware (#14327)
Updated dependencies:
- react-router@7.9.1
- @react-router/node@7.9.1
- @react-router/serve@7.9.1

`v7.9.0`

Compare Source

Minor Changes

Stabilize middleware and context APIs. (#14215)

We have removed the unstable_ prefix from the following APIs and they are now considered stable and ready for production use:
- RouterContextProvider
- [createContext](https://react

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Berlin)

Branch creation
- "every 2 weeks on Monday before 7am"
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.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

vercel · 2025-02-24T04:26:25Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
fairgnuegen	Error		Sep 4, 2026 7:50pm UTC

renovate · 2025-07-10T13:05:39Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: fairgnuegen@0.0.0
npm error Found: @babel/core@7.28.0
npm error node_modules/@babel/core
npm error   dev @babel/core@"7.28.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @babel/core@"^8.0.0" from @babel/plugin-transform-unicode-property-regex@8.0.1
npm error node_modules/@babel/plugin-transform-unicode-property-regex
npm error   dev @babel/plugin-transform-unicode-property-regex@"8.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-04T19_49_58_597Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-04T19_49_58_597Z-debug-0.log

renovate Bot requested review from aeschi, raphael-arce, tsboter and zainab-tariq as code owners February 24, 2025 04:26

vercel Bot had a problem deploying to Preview February 24, 2025 04:26 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from c5be12d to 7e08766 Compare February 25, 2025 12:49

vercel Bot had a problem deploying to Preview February 25, 2025 12:50 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 7e08766 to fe1fa1b Compare February 25, 2025 21:02

vercel Bot had a problem deploying to Preview February 25, 2025 21:02 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from fe1fa1b to dc310b4 Compare March 5, 2025 20:42

vercel Bot had a problem deploying to Preview March 5, 2025 20:42 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from dc310b4 to 2716cb6 Compare March 6, 2025 13:13

vercel Bot had a problem deploying to Preview March 6, 2025 13:13 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 2716cb6 to db0854e Compare March 7, 2025 12:57

vercel Bot had a problem deploying to Preview March 7, 2025 12:57 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from db0854e to 3d5d6d3 Compare March 11, 2025 18:12

vercel Bot had a problem deploying to Preview March 11, 2025 18:12 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 3d5d6d3 to 90a35af Compare March 13, 2025 13:19

vercel Bot had a problem deploying to Preview March 13, 2025 13:19 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 90a35af to 99e4af9 Compare March 21, 2025 01:14

vercel Bot had a problem deploying to Preview March 21, 2025 01:14 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 99e4af9 to d6bda7f Compare March 25, 2025 18:00

vercel Bot had a problem deploying to Preview March 25, 2025 18:01 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from d6bda7f to b0eb760 Compare March 26, 2025 14:49

vercel Bot had a problem deploying to Preview March 26, 2025 14:49 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from b0eb760 to 01f5909 Compare April 1, 2025 17:47

vercel Bot had a problem deploying to Preview April 1, 2025 17:48 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 01f5909 to 621e387 Compare April 2, 2025 10:29

vercel Bot had a problem deploying to Preview April 2, 2025 10:29 Failure

vercel Bot had a problem deploying to Preview May 15, 2025 14:36 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 343ea51 to 209b8c1 Compare May 25, 2025 13:10

vercel Bot had a problem deploying to Preview May 25, 2025 13:10 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 209b8c1 to 88398c7 Compare May 28, 2025 18:08

vercel Bot had a problem deploying to Preview May 28, 2025 18:08 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 88398c7 to fab3994 Compare June 11, 2025 15:17

vercel Bot had a problem deploying to Preview June 11, 2025 15:17 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from fab3994 to 4bf648c Compare June 12, 2025 04:13

vercel Bot had a problem deploying to Preview June 12, 2025 04:13 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 4bf648c to 0e5bb61 Compare June 26, 2025 15:10

vercel Bot had a problem deploying to Preview June 26, 2025 15:11 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 0e5bb61 to 20427ed Compare July 1, 2025 09:59

vercel Bot had a problem deploying to Preview July 1, 2025 09:59 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 20427ed to 5e27641 Compare July 10, 2025 13:05

vercel Bot had a problem deploying to Preview July 10, 2025 13:08 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 5e27641 to c0bd363 Compare July 17, 2025 04:49

vercel Bot had a problem deploying to Preview July 17, 2025 04:49 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from c0bd363 to 3341683 Compare July 22, 2025 15:49

vercel Bot had a problem deploying to Preview July 22, 2025 15:50 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 3341683 to 5d89aa1 Compare August 8, 2025 15:26

vercel Bot had a problem deploying to Preview August 8, 2025 15:28 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 5d89aa1 to 4b64d30 Compare August 14, 2025 15:38

vercel Bot had a problem deploying to Preview August 14, 2025 15:38 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 4b64d30 to 84993c7 Compare August 19, 2025 06:57

vercel Bot had a problem deploying to Preview August 19, 2025 06:57 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 84993c7 to 8a28230 Compare August 28, 2025 03:57

vercel Bot had a problem deploying to Preview August 28, 2025 03:57 Failure

renovate Bot force-pushed the renovate/major-devdependencies-major branch from 8a28230 to e39a478 Compare August 31, 2025 12:06

chore(deps): update devdependencies-major

d999281

Navigation Menu

Uh oh!

chore(deps): update devdependencies-major (major) - #158

chore(deps): update devdependencies-major (major)#158
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-devdependencies-major

renovate Bot commented Feb 24, 2025 •

edited

Loading

Uh oh!

vercel Bot commented Feb 24, 2025 •

edited

Loading

Uh oh!

renovate Bot commented Jul 10, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Server Component Export	Client Component
`ServerComponent`	`default`
`ServerErrorBoundary`	`ErrorBoundary`
`ServerLayout`	`Layout`
`ServerHydrateFallback`	`HydrateFallback`

URL `/a/b/c`	HTTP pathname	`request` pathname`
Document	`/a/b/c`	`/a/b/c` ✅
Data	`/a/b/c.data`	`/a/b/c` ✅

URL `/a/b/c/`	HTTP pathname	`request` pathname`
Document	`/a/b/c/`	`/a/b/c/` ✅
Data	`/a/b/c.data`	`/a/b/c` ⚠️

Uh oh!

Conversation

renovate Bot commented Feb 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

💥 Breaking Change

👓 Spec Compliance

💥 Breaking Change

🐛 Bug Fix

📝 Documentation

🏠 Internal

🏃‍♀️ Performance

v7.29.7 (2026-05-25)

v7.28.6 (2026-01-12)

🐛 Bug Fix

💅 Polish

🏠 Internal

🏃‍♀️ Performance

Committers: 7

Minor Changes

Patch Changes

Unstable Changes

Migration guide

Minor Changes

Patch Changes

Unstable Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Unstable Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Unstable Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Configuration

Uh oh!

vercel Bot commented Feb 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

renovate Bot commented Jul 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: package-lock.json

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Feb 24, 2025 •

edited

Loading

vercel Bot commented Feb 24, 2025 •

edited

Loading

renovate Bot commented Jul 10, 2025 •

edited

Loading