fix(deps): update react-router monorepo to v8#43
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
e311b5a to
614dcfe
Compare
614dcfe to
3a24b37
Compare
3a24b37 to
2099978
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.14.2→^8.0.0^7.14.2→^8.0.0^7.14.2→^8.0.0^7.14.2→^8.0.0Release Notes
remix-run/react-router (@react-router/dev)
v8.2.0Compare Source
Minor Changes
@react-router/node,@react-router/express, or@react-router/servecontinue to use therenderToPipeableStreamdefault server entryrenderToReadableStreamdefault server entryentry.server.tsxmay be able to remove it in favor of the default if it is not doing anything customnubas a supported package manager when installing framework dependencies (#15276)Patch Changes
rolldownOptionsconfig in Vite 8+ (#15278)Unstable Changes
future.unstable_enableNodeReadableStreamflag to opt Node Framework mode apps into usingrenderToReadableStreaminstead ofrenderToPipeableStream(#15290)entry.server.tsxreact-router@8.2.0@react-router/node@8.2.0@react-router/serve@8.2.0v8.1.0Compare Source
Patch Changes
react-router.config.tsbuildEndhook would run before prerendering was completed (#15211)react-router typegencrashes under the Bun runtime when Babel default imports are already unwrapped (#15214)envFile:falseVite config withenvDir:falseto eliminate a deprecation warning when using vite@8.1.0+ (#15230)"node"Vite server condition for Framework mode apps that declare a Node server adapter dependency (#15242)react-router@8.1.0@react-router/node@8.1.0@react-router/serve@8.1.0v8.0.1Compare Source
Patch Changes
react-router@8.0.1@react-router/node@8.0.1@react-router/serve@8.0.1v8.0.0Compare Source
Major Changes
@react-router/dev/vite/cloudflaredev proxy export; use@cloudflare/vite-plugininstead (#15077)wrangler@3as a peer dependency of@react-router/devfuture.v8_trailingSlashAwareDataRequestsflag (#15100)future.v8_passThroughRequestsflag - the raw incomingrequestis now always passed through toloader/action. (#15079)future.v8_splitRouteModulesto a top-levelsplitRouteModulesconfig option and change the default behavior totrue(#15086)splitRouteModules: falseto keep route modules in a single chunksplitRouteModules: "enforce"to require all routes to be splittablefuture.v8_viteEnvironmentApiflag because the Vite Environment API is always enabled (#15077)future.unstable_previewServerPrerenderingflag and make prerendering with the Vite Environment API the default. (#15077)Minor Changes
@babel/corefrom^7.27.7to^7.29.7@babel/generatorfrom^7.27.5to^7.29.7@babel/parserfrom^7.27.7to^7.29.7@babel/plugin-syntax-jsxfrom^7.27.1to^7.29.7@babel/preset-typescriptfrom^7.27.1to^7.29.7@babel/traversefrom^7.27.7to^7.29.7@babel/typesfrom^7.27.7to^7.29.7dedentfrom^1.5.3to^1.7.2jsescfrom3.0.2to3.1.0lodashfrom^4.17.21to^4.18.1prettierfrom^3.6.2to^3.8.3@remix-run/node-fetch-serverfrom^0.13.0to^0.13.3react-refreshfrom^0.14.0to^0.18.0semverfrom^7.3.7to^7.8.1tinyglobbyfrom^0.2.14to^0.2.16valibotfrom^1.2.0to^1.4.1cookieandset-cookie-parserwithcookie-es(#15109)vite-nodedependency in favor of Vite's native module runner APIs (#15104)Patch Changes
@babel/corefrom^7.29.0to^7.29.7@babel/generatorfrom^7.29.1to^7.29.7@babel/parserfrom^7.29.3to^7.29.7@babel/plugin-syntax-jsxfrom^7.28.6to^7.29.7@babel/preset-typescriptfrom^7.28.5to^7.29.7@babel/traversefrom^7.29.0to^7.29.7@babel/typesfrom^7.29.0to^7.29.7babel-dead-code-eliminationfrom^1.0.6to^1.0.12chokidarfrom^4.0.0to^5.0.0es-module-lexerfrom^1.3.1to^2.1.0exit-hookfrom2.2.1to5.1.0isbotfrom^5.1.11to^5.1.40p-mapfrom^7.0.3to^7.0.4pathefrom^1.1.2to^2.0.3pkg-typesfrom^2.3.0to^2.3.1react-refreshfrom^0.14.0to^0.18.0semverfrom^7.8.0to^7.8.1tinyglobbyfrom^0.2.14to^0.2.16valibotfrom^1.4.0to^1.4.1!(handle->flags & UV_HANDLE_CLOSING)insrc/win/async.c) during prerendering by usingnode:httpinstead offetchfor internal prerender requests against the Vite preview server (#15077)react-router@8.0.0@react-router/node@8.0.0@react-router/serve@8.0.0remix-run/react-router (@react-router/fs-routes)
v8.2.0Compare Source
Patch Changes
@react-router/dev@8.2.0v8.1.0Compare Source
Patch Changes
@react-router/dev@8.1.0v8.0.1Compare Source
Patch Changes
@react-router/dev@8.0.1v8.0.0Compare Source
Major Changes
Patch Changes
minimatchfrom^9.0.0to^10.2.5@react-router/dev@8.0.0remix-run/react-router (@react-router/node)
v8.2.0Compare Source
Patch Changes
react-router@8.2.0v8.1.0Compare Source
Patch Changes
react-router@8.1.0v8.0.1Compare Source
Patch Changes
react-router@8.0.1v8.0.0Compare Source
Major Changes
@mjackson/node-fetch-serverto@remix-run/node-fetch-servernow that we can directly use ESM-only packages (#14930)Patch Changes
@remix-run/node-fetch-serverfrom^0.13.0to^0.13.3react-router@8.0.0remix-run/react-router (react-router)
v8.2.0Compare Source
Patch Changes
href()to properly stringify and URL-encode param values, matchinggeneratePath()(#15277)/school?/user/:id), the internal regex's incorrectly shifted parameter indices resulting in incorrect parameter extraction/one?/two?) were only partially handled/sitemap.xmland outrank them based on definition orderv8.1.0Compare Source
Minor Changes
v8.0.1Compare Source
Patch Changes
AppLoadContexttype export accidentally left over from v7 now that middleware is always enabled and server request context is provided throughRouterContextProvider. (#15207)v8.0.0Compare Source
Major Changes
future.v8_trailingSlashAwareDataRequestsflag (#15100)tsconfig.jsontarget/libfromES2020 -> ES2022(591853e)packages/to ESM-only. (#14895) (59ebcf1)dataparameter in favor ofloaderDataformetaAPIs (to align withRoute.ComponentProps) (#14931)Route.MetaArgs,Route.MetaMatch,MetaArgs,MetaMatch,Route.ComponentProps.matches,UIMatchfuture.v8_passThroughRequestsflag - the raw incomingrequestis now always passed through toloader/action. Useurlfor the normalized URL without React Router-specific implementation details (.datasuffixes,index/_routessearch params). (#15079)hasErrorBoundaryfield added torouter.routeswhen using a data router (#15074)ErrorBoundaryorerrorElementon your routehasErrorBoundaryis no longer accepted onRouteObject(IndexRouteObject/NonIndexRouteObject),DataRouteObject,<Route>JSX props, or as a key inlazyroute definitions.MapRoutePropertiesFunctionsignature no longer requires returninghasErrorBoundary; the router infers it directly.react-router-dompackage (#15076)react-router/domreact-router-domwas kept around as a convenience so existing v6 app imports would still workreact-router-domimports:RouterProvider/HydratedRoutershould be imported fromreact-router/domreact-routerfuture.v8_middlewareflag — middleware is always enabled in v8 (#15078)future.v8_middlewareflag has been removed; middleware is now always enabledcontextparameter passed toloader,action, andmiddlewarefunctions is always aRouterContextProviderinstancegetLoadContextfunctions in custom servers must return aRouterContextProvider— returning a plain object is no longer supportedMiddlewareEnabledtype (previously exported asUNSAFE_MiddlewareEnabled) has been removed since the conditional it gated is now unconditionalFuturemodule augmentation pattern (interface Future { v8_middleware: true }) is no longer needed to typecontextin Data ModeMinor Changes
cookiefrom^1.0.1to^1.1.1set-cookie-parserfrom^2.6.0to^3.1.0Patch Changes
onSubmittype override fromSharedFormPropsto fix deprecation warning with@types/react@19.x(#14932) (59ebcf1)tsuptotsdown. Published package entry points and public APIs are unchanged. (#15092)Configuration
📅 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.