v8.0.1

Compare Source

Patch Changes

• Remove the obsolete AppLoadContext type export accidentally left over from v7 now that middleware is always enabled and server request context is provided through RouterContextProvider. (#​15207)

v8.0.0

Compare Source

Major Changes

• Remove the future.v8_trailingSlashAwareDataRequests flag (#​15100)
  • Trailing slash-aware data request URLs are now the default behavior.
• Update tsconfig.json target/lib from ES2020 -> ES2022 (591853e)
• Switch the published packages in packages/ to ESM-only. (#​14895) (59ebcf1)
• Remove deprecated data parameter in favor of loaderData for meta APIs (to align with Route.ComponentProps) (#​14931)
  • Route.MetaArgs, Route.MetaMatch, MetaArgs, MetaMatch, Route.ComponentProps.matches, UIMatch
• Remove future.v8_passThroughRequests flag - the raw incoming request is now always passed through to loader/action. Use url for the normalized URL without React Router-specific implementation details (.data suffixes, index/_routes search params). (#​15079)
• Remove internal hasErrorBoundary field added to router.routes when using a data router (#​15074)
  • This should not impact user-facing code since this was an internal prop and was computed based on the presence of ErrorBoundary or errorElement on your route
  • hasErrorBoundary is no longer accepted on RouteObject (IndexRouteObject/NonIndexRouteObject), DataRouteObject, <Route> JSX props, or as a key in lazy route definitions.
  • The MapRoutePropertiesFunction signature no longer requires returning hasErrorBoundary; the router infers it directly.
• Remove react-router-dom package (#​15076)
  • In v7 everything DOM-specific was collapsed into react-router/dom
    • react-router-dom was kept around as a convenience so existing v6 app imports would still work
  • For v8, you will need to swap react-router-dom imports:
    • RouterProvider/HydratedRouter should be imported from react-router/dom
    • Everything else should be imported from react-router
• Remove future.v8_middleware flag — middleware is always enabled in v8 (#​15078)
  • The future.v8_middleware flag has been removed; middleware is now always enabled
  • The context parameter passed to loader, action, and middleware functions is always a RouterContextProvider instance
  • getLoadContext functions in custom servers must return a RouterContextProvider — returning a plain object is no longer supported
  • The MiddlewareEnabled type (previously exported as UNSAFE_MiddlewareEnabled) has been removed since the conditional it gated is now unconditional
  • The Future module augmentation pattern (interface Future { v8_middleware: true }) is no longer needed to type context in Data Mode
• Update minimum Node version to 22.22.0 (#​14928)
• Update minimum React version to 19.2.7 (#​15062)

Minor Changes

• Bump dependencies (#​15080)
  • Bumped cookie from ^1.0.1 to ^1.1.1
  • Bumped set-cookie-parser from ^2.6.0 to ^3.1.0

Patch Changes

• Ensure client middleware errors load lazy route error boundaries before bubbling (#​15086)
• Remove explicit onSubmit type override from SharedFormProps to fix deprecation warning with @types/react@19.x (#​14932) (59ebcf1)
• Update package builds to preserve individual module files in published artifacts. Public APIs and documented import paths are unchanged. (#​15092)
  • Updated package TypeScript configs to support modern module syntax used by the build configuration.
• Migrate package builds from tsup to tsdown. Published package entry points and public APIs are unchanged. (#​15092)
• Upgrade React Router's TypeScript tooling to TypeScript 6. Runtime behavior and public APIs are unchanged. (#​15092)