@depup/tanstack__react-router 1.167.5-depup.0 → 1.168.2-depup.0

package/dist/llms/rules/api.js

@@ -1841,7 +1841,6 @@ type RouterState = {
   isLoading: boolean
   isTransitioning: boolean
   matches: Array<RouteMatch>
-  pendingMatches: Array<RouteMatch>
   location: ParsedLocation
   resolvedLocation: ParsedLocation
 }
@@ -1871,11 +1870,6 @@ The \`RouterState\` type contains all of the properties that are available on th
 - Type: [\`Array<RouteMatch>\`](./RouteMatchType.md)
 - An array of all of the route matches that have been resolved and are currently active.
 
-### \`pendingMatches\` property
-
-- Type: [\`Array<RouteMatch>\`](./RouteMatchType.md)
-- An array of all of the route matches that are currently pending.
-
 ### \`location\` property
 
 - Type: [\`ParsedLocation\`](./ParsedLocationType.md)
@@ -3350,14 +3344,14 @@ If \`true\` is passed in, all search params will be retained.
 \`\`\`tsx
 import { z } from 'zod'
 import { createRootRoute, retainSearchParams } from '@tanstack/react-router'
-import { zodValidator } from '@tanstack/zod-adapter'
 
 const searchSchema = z.object({
   rootValue: z.string().optional(),
 })
 
 export const Route = createRootRoute({
-  validateSearch: zodValidator(searchSchema),
+  // Use the schema directly for Zod v4
+  validateSearch: searchSchema,
   search: {
     middlewares: [retainSearchParams(['rootValue'])],
   },
@@ -3367,7 +3361,6 @@ export const Route = createRootRoute({
 \`\`\`tsx
 import { z } from 'zod'
 import { createFileRoute, retainSearchParams } from '@tanstack/react-router'
-import { zodValidator } from '@tanstack/zod-adapter'
 
 const searchSchema = z.object({
   one: z.string().optional(),
@@ -3375,7 +3368,8 @@ const searchSchema = z.object({
 })
 
 export const Route = createFileRoute('/')({
-  validateSearch: zodValidator(searchSchema),
+  // Use the schema directly for Zod v4
+  validateSearch: searchSchema,
   search: {
     middlewares: [retainSearchParams(true)],
   },
@@ -3451,7 +3445,6 @@ const router = createRouter({
 \`\`\`tsx
 import { z } from 'zod'
 import { createFileRoute, stripSearchParams } from '@tanstack/react-router'
-import { zodValidator } from '@tanstack/zod-adapter'
 
 const defaultValues = {
   one: 'abc',
@@ -3464,7 +3457,8 @@ const searchSchema = z.object({
 })
 
 export const Route = createFileRoute('/')({
-  validateSearch: zodValidator(searchSchema),
+  // for Zod v4, use the schema directly
+  validateSearch: searchSchema,
   search: {
     // strip default values
     middlewares: [stripSearchParams(defaultValues)],
@@ -3475,7 +3469,6 @@ export const Route = createFileRoute('/')({
 \`\`\`tsx
 import { z } from 'zod'
 import { createRootRoute, stripSearchParams } from '@tanstack/react-router'
-import { zodValidator } from '@tanstack/zod-adapter'
 
 const searchSchema = z.object({
   hello: z.string().default('world'),
@@ -3483,7 +3476,8 @@ const searchSchema = z.object({
 })
 
 export const Route = createRootRoute({
-  validateSearch: zodValidator(searchSchema),
+  // for Zod v4, use the schema directly
+  validateSearch: searchSchema,
   search: {
     // always remove \`hello\`
     middlewares: [stripSearchParams(['hello'])],
@@ -3494,7 +3488,6 @@ export const Route = createRootRoute({
 \`\`\`tsx
 import { z } from 'zod'
 import { createFileRoute, stripSearchParams } from '@tanstack/react-router'
-import { zodValidator } from '@tanstack/zod-adapter'
 
 const searchSchema = z.object({
   one: z.string().default('abc'),
@@ -3502,7 +3495,8 @@ const searchSchema = z.object({
 })
 
 export const Route = createFileRoute('/')({
-  validateSearch: zodValidator(searchSchema),
+  // for Zod v4, use the schema directly
+  validateSearch: searchSchema,
   search: {
     // remove all search params
     middlewares: [stripSearchParams(true)],
@@ -3797,7 +3791,7 @@ function Component() {
 The \`useChildMatches\` hook returns all of the child [\`RouteMatch\`](./RouteMatchType.md) objects from the closest match down to the leaf-most match. **It does not include the current match, which can be obtained using the \`useMatch\` hook.**
 
 > [!IMPORTANT]
-> If the router has pending matches and they are showing their pending component fallbacks, \`router.state.pendingMatches\` will used instead of \`router.state.matches\`.
+> If the router has pending matches and they are showing their pending component fallbacks, pending matches are used instead of active matches.
 
 ## useChildMatches options
 
@@ -4406,7 +4400,7 @@ function Component() {
 The \`useParentMatches\` hook returns all of the parent [\`RouteMatch\`](./RouteMatchType.md) objects from the root down to the immediate parent of the current match in context. **It does not include the current match, which can be obtained using the \`useMatch\` hook.**
 
 > [!IMPORTANT]
-> If the router has pending matches and they are showing their pending component fallbacks, \`router.state.pendingMatches\` will used instead of \`router.state.matches\`.
+> If the router has pending matches and they are showing their pending component fallbacks, pending matches are used instead of active matches.
 
 ## useParentMatches options
 
@@ -4514,7 +4508,7 @@ function Component() {
 The \`useRouterState\` method is a hook that returns the current internal state of the router. This hook is useful for accessing the current state of the router in a component.
 
 > [!TIP]
-> If you want to access the current location or the current matches, you should try out the [\`useLocation\`](./useLocationHook.md) and [\`useMatches\`](./useMatchesHook.md) hooks first. These hooks are designed to be more ergonomic and easier to use than accessing the router state directly.
+> If you want to access the current location or the current matches, you should try out the [\`useLocation\`](./useLocationHook.md) and [\`useMatches\`](./useMatchesHook.md) hooks first. These hooks are designed to be more performant, more ergonomic and easier to use than accessing the router state directly.
 
 ## useRouterState options