Repository navigation
chore(deps): update dependency react-router-dom to v7.18.6 - #105
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
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
March 23, 2026 14:08
084402d to
a9674ab
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
April 2, 2026 21:11
a9674ab to
d6d61a9
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
April 13, 2026 21:40
d6d61a9 to
e41ce95
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
April 21, 2026 20:19
e41ce95 to
ad459d4
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
May 5, 2026 19:34
ad459d4 to
1b12c48
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
May 14, 2026 16:39
1b12c48 to
4994d14
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
May 28, 2026 21:38
4994d14 to
e86eb61
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 4, 2026 15:00
e86eb61 to
da2ede6
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 16, 2026 18:05
da2ede6 to
e11a9bf
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
June 29, 2026 23:36
e11a9bf to
1a93eaf
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
July 12, 2026 17:52
1a93eaf to
e4d23a8
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
July 20, 2026 23:07
e4d23a8 to
1e54fb6
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
July 28, 2026 22:30
1e54fb6 to
666c2c2
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
August 28, 2026 16:09
666c2c2 to
29f13a1
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
September 15, 2026 22:02
29f13a1 to
c2de6f6
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
October 26, 2026 23:16
c2de6f6 to
66a58b3
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
October 27, 2026 23:37
66a58b3 to
7b1166b
Compare
renovate
Bot
force-pushed
the
renovate/react-router-monorepo
branch
from
November 19, 2026 04:36
7b1166b to
ded796c
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.
This PR contains the following updates:
7.13.0→7.18.6Release Notes
remix-run/react-router (react-router-dom)
v7.18.6Compare Source
v7.18.5Compare Source
v7.18.4Compare Source
v7.18.3Compare Source
v7.18.2Compare Source
v7.18.1Compare Source
v7.18.0Compare Source
Date: 2026-06-16
What's Changed
CSRF Check Logic Fix
We made a bug fix in our underlying CSRF checks in this release that may be a "breaking bug fix" for some users deployed behind a reverse proxy. The CSRF check now checks directly against the
hostin therequesturl provided, instead of looking directly at HTTP headers which is an adapter concern. If your adapter is not setting the expected host in the request URL, you may need to add the new internal host to yourallowedActionOriginsconfig. This is most likely to occur in@react-router/serveapps or@react-router/expressapps without thetrust proxysetting enabled. We recommend testing this against application mutation requests as part of your upgrade.Minor Changes
@react-router/architect- Add auseRequestContextDomainNameoption tocreateRequestHandlerto derive request URL hosts from the API Gateway request context (#15185)Patch Changes
react-router- Fix server handler prerender responses when usingssr: falseandfuture.v8_trailingSlashAwareDataRequests: true(#15173)react-router- Use theServerRouternoncefor nonce-aware SSR components when they don't provide their own value so strict CSP pages can load them (#15170)react-router- Useturbo-streamto serialize and deserialize Framework Mode hydration errors (#15175)react-router- Optimize route matching by extending precomputed route branches to include matchers (#15186)react-router- Use the constructedrequestURLhostinstead of header checks when validating action request origins in the CSRF check (#15185)react-router- Remove the un-documented custom error serialization logic from Data Mode SSR built-in hydration flows (#15175)react-router- Validate protocols in RSC render redirects (#15177)react-router- Consolidate url normalization logic and better handle mixed slashes (#15176)@react-router/dev- Pass Viteserver.watchconfig to child compiler in development mode. (#15178)@react-router/dev- Ignore external Vite server environments in Framework Mode build hooks (#14883)future.v8_viteEnvironmentApiis enabled, React Router previously treated any non-client Vite environment as its own server build@react-router/express- Adjust express adapter host computation (#15185)x-forwarded-hostbased ontrust proxysettingFull Changelog:
v7.17.0...v7.18.0v7.17.0Compare Source
Date: 2026-06-04
Minor Changes
react-router- Ship a subset of the official documentation inside thereact-routerpackage (#15121)node_modules/react-router/docs, letting AI coding agents and the React Router agent skills read official docs locallyapi/),community/content, and tutorials (tutorials/)Patch Changes
@react-router/dev- Fix future flag warning URLs and only log each future flag warning one time (#15138)Unstable Changes
@react-router/dev- Prevent RSC route module server exports from being scanned by the client dependency optimizer whenfuture.unstable_optimizeDepsis enabled. (#15005)Full Changelog:
v7.16.0...v7.17.0v7.16.0Compare Source
Date: 2026-05-28
Minor Changes
react-router- Stabilizefuture.unstable_trailingSlashAwareDataRequestsasfuture.v8_trailingSlashAwareDataRequests(#15098)@react-router/dev- Stabilizefuture.unstable_trailingSlashAwareDataRequestsasfuture.v8_trailingSlashAwareDataRequests(#15098)@react-router/dev- Log future flag warnings for upcoming React Router v8 flags (#15029)v8_middleware,v8_splitRouteModules,v8_viteEnvironmentApi,v8_passThroughRequests,v8_trailingSlashAwareDataRequestsPatch Changes
react-router- Disable manifest path when lazy route dicovery is disabled (#15068)react-router- Fix browser URL creation to use the configured history window instead of the global window. (#15066)createBrowserURLImplso custom window contexts keep the correct URL origin.react-router- FixuseNavigation()return type to preserve discriminated union across navigation states (#15095)react-router- WidenMetaDescriptorscript:ld+jsontype fromLdJsonObjecttoLdJsonObject | LdJsonObject[]to permit multiple JSON-LD schemas in a single<script type="application/ld+json">tag emitted by<Meta />(#15082)react-router-dom- Remove stale/invalidunpkgfield frompackage.json. This was removed from other packages with the release of v7 but missed in thereact-router-domre-export package (#15075)@react-router/express- Ignore writes after Express responses close (#15107)@react-router/node- Honor Node writable backpressure inwriteReadableStreamToWritableandwriteAsyncIterableToWritable(#15071)'drain'whenwritable.write()returnsfalseinstead of letting chunks accumulate in the writable's internal buffer.@react-router/serve- NormalizeassetsBuildDirectorypath separators inreact-router-serveso Windows-built server artifacts can serve/assets/*correctly when run on Linux. (#14982)Full Changelog:
v7.15.1...v7.16.0v7.15.1Compare Source
Date: 2026-05-14
What's New
useRouterState(unstable)Following our Less is More design goal, this release includes a new
unstable_useRouterState()hook (Framework + Data Mode) that consolidates access to active and pending router states (RFC, Roadmap Issue).This should allow you to consolidate usages of a bunch of different hooks which will likely be marked deprecated later on in v8 and potentially removed in an eventual v9:
Patch Changes
react-router- MemoizeuseFetchersto return a stable identity and only change if fetchers changed (#15028)react-router- Update router to operate on fetcher Maps in an immutable manner to avoid delayed React renders from potentially reading an updated but not yet committed Map. This could result in brief flickers in some fetcher-driven optimistic UI scenarios (#15028)react-router- FixserverLoader()returning stale SSR data when a client navigation aborts pending hydration before the hydrationclientLoaderresolves (#15022)react-router- FixRouterProvideronErrorcallback not being called for synchronous initial loader errors in SPA mode (#15039) (#14942)react-router- Internal refactor to consolidate mutation request detection through shared utility (#15033)@react-router/dev- Fixbasenameconflicting withappdirectory name when Vitebaseis set (#15027)baseconfig and React Routerbasenameboth 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/@fs/absolute paths for those imports to bypass Vite's base-stripping logicUnstable Changes
react-router- Add a newunstable_useRouterState()hook that consolidates access to active and pending router states (RFC: #12358) (#15017)Full Changelog:
v7.15.0...v7.15.1v7.15.0Compare Source
Date: 2026-05-05
What's Changed
Stabilizations
We've stabilized a bunch of APIs in this release in preparation for a React Router v8 release hopefully in the next month or two. These flag/prop renames are breaking changes if you've already opted into the unstable APIs so please make sure you make the appropriate changes if so.
future.unstable_passThroughRequests→future.v8_passThroughRequestsfuture.unstable_subResourceIntegrity→ top-levelconfig.subResourceIntegrityprerender.unstable_concurrency→prerender.concurrencyunstable_url→url(loader, action, middleware, instrumentation args)unstable_instrumentations→instrumentationsServerInstrumentation,ClientInstrumentation, etc.)unstable_pattern→pattern(loader, action, middleware, instrumentation args)unstable_defaultShouldRevalidate→defaultShouldRevalidateunstable_useTransitions→useTransitionsunstable_mask→mask(on<Link>,useLinkClickHandler,useNavigate, andLocation)Route matching optimizations
We've added a handful of route matching optimizations in this release for Framework and Data mode. The changes are mostly related to caching the internal flattened/ranked route branches and reducing additional calls to
matchRoutesalong the critical path. This should result in improved performance during both server-side request handling and client-side navigations.Minor Changes
react-router- Stabilizeunstable_defaultShouldRevalidateasdefaultShouldRevalidateon<Link>,<Form>,useLinkClickHandler,useSubmit,fetcher.submit, andsetSearchParams(14999)react-router- Stabilize the instrumentation APIs (14999)unstable_instrumentationsis nowinstrumentationsunstable_patternis nowpatternunstable_ServerInstrumentation,unstable_ClientInstrumentation,unstable_InstrumentRequestHandlerFunction,unstable_InstrumentRouterFunction,unstable_InstrumentRouteFunction, andunstable_InstrumentationHandlerResulttypes have had theirunstable_prefixes removedreact-router- Stabilizeunstable_maskasmaskon<Link>,useLinkClickHandler, anduseNavigate, and rename the correspondingLocation.unstable_maskfield toLocation.mask(14999)react-router- Stabilize theunstable_normalizePathoption onstaticHandler.queryandstaticHandler.queryRouteasnormalizePath(14999)react-router- Stabilizefuture.unstable_passThroughRequestsasfuture.v8_passThroughRequests(14999)react-router- Removeunstable_subResourceIntegrityfrom the runtimeFutureConfigtype; the flag is now controlled by the top-levelsubResourceIntegrityoption inreact-router.config.ts(14999)react-router- Stabilizeunstable_urlasurlonloader,action, andmiddlewarefunction args (14999)react-router- Stabilizeunstable_useTransitionsasuseTransitionson<BrowserRouter>,<HashRouter>,<HistoryRouter>,<MemoryRouter>,<Router>,<RouterProvider>,<HydratedRouter>, anduseLinkClickHandler(14999)@react-router/dev- Stabilizefuture.unstable_passThroughRequestsasfuture.v8_passThroughRequests(14999)@react-router/dev- Stabilizeprerender.unstable_concurrencyasprerender.concurrency(14999)@react-router/dev- Stabilizefuture.unstable_subResourceIntegrityas a top-levelsubResourceIntegrityconfig option inreact-router.config.ts(14999)Patch Changes
react-router- Addnonceto<Scripts><link rel="modulepreload">elements (if provided) (af5d49b)react-router- Fix a bug withunstable_defaultShouldRevalidate={false}where parent routes that did not export ashouldRevalidatefunction could be incorrectly included in the single fetch call for new child route data (#15012)react-router- Markmaskas an optional field inLocationfor easier mocking in unit tests (#14999)react-router- Improve server-side route matching performance by pre-computing flattened/cached route branches (#14967)react-router- Cache flattened/ranked route branches to optimize server-side route matching (#14967)react-router- Improve route matching performance in Framework/Data Mode (#14971)matchRoutesin data router scenarios7.6.0(#13562)matchesbut always updatingmatch.routeto the latest route in themanifestFull Changelog:
v7.14.2...v7.15.0v7.14.2Compare Source
Date: 2026-04-21
Patch Changes
react-router- Remove the un-documented custom error serialization logic from the internal turbo-stream implementation. React Router only automatically handles serialization ofErrorand it's standard subtypes (SyntaxError,TypeError, etc.). (#14992)react-router- Properly handle parent middleware redirects duringfetcher.load(#14974)react-router- Remove redundantOmit<RouterProviderProps, "flushSync">fromreact-router/domRouterProvider(#14874)react-router- Improved types forgeneratePath'sparamarg (#14984)Type errors when required params are omitted:
Allow omission of optional params:
Allows extra keys:
@react-router/dev- Fix typegen for layouts without pages (#14875)pages: ;in.react-router/types/+routes.tswhen a route corresponded to 0 pagespages: never;is correctly generated for those casesUnstable Changes
@react-router/dev- Forunstable_reactRouterRSCVite plugin consumers, require@vitejs/plugin-reactin user Vite config, and more reliably split route modules (#14965)unstable_reactRouterRSCVite plugin - please install@vitejs/plugin-reactand add thereactplugin to your Vite plugins array.Full Changelog:
v7.14.1...v7.14.2v7.14.1Compare Source
Date: 2026-04-13
Patch Changes
react-router- Fix a potential race condition that can occur when rendering aHydrateFallbackand initial loaders land before therouter.subscribecall happens in theRouterProviderlayout effect (#14497)react-router- Normalize double-slashes in redirect paths (#14962)@react-router/dev- Add TypeScript 6 support to peer dependency ranges (#14935)Full Changelog:
v7.14.0...v7.14.1v7.14.0Compare Source
Date: 2026-04-02
Minor Changes
Patch Changes
react-router- Remove recursion from vendoredturbo-streamv2 implementation allowing for encoding/decoding of large payloads (#14838)react-router- FixencodeViaTurboStreammemory leak via unremovedAbortSignallistener (#14900)@react-router/dev- Support for prerendering multiple server bundles withv8_viteEnvironmentApi(#14921)Unstable Changes
@react-router/dev- Pre-rendering and SPA Mode support for RSC Framework Mode (#14907)@react-router/dev- Updatereact-router revealto support RSC Framework Mode forentry.client,entry.rsc,entry.ssr(#14904)react-router- Support<Link prefetch>in RSC Framework Mode (#14902)react-router- Add support for new route module exports in unstable RSC Framework Mode (#14901)The following route module components have their own mutually exclusive server component counterparts:
defaultServerComponentErrorBoundaryServerErrorBoundaryLayoutServerLayoutHydrateFallbackServerHydrateFallbackIf you were previously exporting a
ServerComponent, yourErrorBoundary,Layout, andHydrateFallbackwere also implicitly server componentsIf you want to keep those as server components - rename them and prefix them with
ServerIf you were previously importing the implementations of those components from a client module, you can inline them
Full Changelog:
v7.13.2...v7.14.0v7.13.2Compare Source
Date: 2026-03-23
What's Changed
Pass-through Requests (unstable)
By default, React Router normalizes the
request.urlpassed to yourloader,action, andmiddlewarefunctions by removing React Router's internal implementation details (.datasuffixes,index+_routesquery params). This release introduces a newfuture.unstable_passThroughRequestsflag to disable this normalization and pass the raw HTTPrequestinstance to your handlers.In addition to reducing server-side overhead by eliminating multiple
new Request()calls on the critical path, this also provides additional visibility to your route handlers/instrumentations allowing you to differentiate document from data requests.If you were previously relying on the normalization of
request.url, you can switch to use the new siblingunstable_urlparameter which contains aURLinstance representing the normalized location:Route handlers/middleware
unstable_urlparameterWe have added a new
unstable_url: URLparameter to route handler methods (loader,action,middleware, etc.) that contains the normalized URL the application is navigating to or fetching with React Router implementation details removed (.datasuffix,index/_routesquery params).This parameter is primarily needed when adopting the new
future.unstable_passthroughRequestsfuture flag as a way to continue accessing the normalized URL. If you don't have the flag enabled, thenunstable_urlwill matchrequest.url.Patch Changes
react-router- FixclientLoader.hydratewhen an ancestor route is also hydrating aclientLoader(#14835)react-router- Fix type error when passing Framework Mode route components usingRoute.ComponentPropstocreateRoutesStub(#14892)react-router- Fix percent encoding in relative path navigation (#14786)react-router- Internal refactor to consolidate framework-agnostic/React-specific route type layers - no public API changes (#14765)@react-router/dev- Fixreact-router devcrash when Unix socket files exist in the project root (#14854)@react-router/dev- Escape redirect locations in pre-rendered redirect HTML (#14880)create-react-router- replacechalkwithpicocolors(#14837)Unstable Changes
react-router- Sync protocol validation to RSC flows (#14882)react-router- Addfuture.unstable_passThroughRequestsflag (#14775)react-router- Add a newunstable_url: URLparameter 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/_routesquery params) (#14775)Full Changelog:
v7.13.1...v7.13.2v7.13.1Compare Source
Date: 2026-02-23
What's Changed
URL Masking (unstable)
This release includes a new
<Link unstable_mask>API which brings first-class support for URL masking to Framework/Data Mode (RFC). This allows the same type of UI you could achieve in Declarative Mode via manualbackgroundLocationmanagement. That example has been converted to Data Mode using the new API here.Patch Changes
react-router- Clear timeout whenturbo-streamencoding completes (#14810)react-router- Improve error message whenOriginheader is invalid (#14743)react-router- FixmatchPathoptional params matching without a"/"separator. (#14689)matchPath("/users/:id?", "/usersblah")now returns nullmatchPath("/test_route/:part?", "/test_route_more")now returns null.react-router- FixHydrateFallbackrendering during initial lazy route discovery with matching splat route (#14740)react-router- Preserve query parameters and hash on manifest version mismatch reload (#14813)Unstable Changes
react-router- RSC: fix null reference exception in bad codepath leading to invalid route tree comparisons (#14780)react-router- RSC: addunstable_getRequestAPI (#14758)react-router- RSC: Update failed origin checks to return a 400 status and appropriate UI instead of a generic 500 (#14755)react-router- Add support for<Link unstable_mask>in Framework/Data Mode which allows users to navigate to a URL in the router but "mask" the URL displayed in the browser (#14716)This is useful for contextual routing usages such as displaying an image in a modal on top of a gallery, but displaying a browser URL directly to the image that can be shared and loaded without the contextual gallery in the background
The masked location, if present, will be available on
useLocation().unstable_maskso you can detect whether you are currently masked or notMasked URLs only work for SPA use cases, and will be removed from
history.stateduring SSRThis provides a first-class API to mask URLs in Framework/Data Mode to achieve the same behavior you could do in Declarative Mode via manual
backgroundLocationmanagement.Full Changelog:
v7.13.0...v7.13.1Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.