@tanstack/react-router 1.130.8 → 1.130.10

package/dist/llms/rules/guide.js

@@ -168,9 +168,9 @@ This approach can also be used in conjunction with Pathless or Layout Route to p
 
 For detailed, step-by-step implementation guides, see:
 
-- [How to Set Up Basic Authentication](../how-to/setup-authentication.md) - Complete setup with React Context and protected routes
-- [How to Integrate Authentication Providers](../how-to/setup-auth-providers.md) - Use Auth0, Clerk, or Supabase
-- [How to Set Up Role-Based Access Control](../how-to/setup-rbac.md) - Implement permissions and role-based routing
+- [How to Set Up Basic Authentication](../../how-to/setup-authentication.md) - Complete setup with React Context and protected routes
+- [How to Integrate Authentication Providers](../../how-to/setup-auth-providers.md) - Use Auth0, Clerk, or Supabase
+- [How to Set Up Role-Based Access Control](../../how-to/setup-rbac.md) - Implement permissions and role-based routing
 
 ## Examples
 
@@ -1292,7 +1292,10 @@ export const Route = createFileRoute('/posts')({
 The \`loader\` function receives a single object with the following properties:
 
 - \`abortController\` - The route's abortController. Its signal is cancelled when the route is unloaded or when the Route is no longer relevant and the current invocation of the \`loader\` function becomes outdated.
-- \`cause\` - The cause of the current route match, either \`enter\` or \`stay\`.
+- \`cause\` - The cause of the current route match. Can be either one of the following:
+  - \`enter\` - When the route is matched and loaded after not being matched in the previous location.
+  - \`preload\` - When the route is being preloaded.
+  - \`stay\` - When the route is matched and loaded after being matched in the previous location.
 - \`context\` - The route's context object, which is a merged union of:
   - Parent route context
   - This route's context as provided by the \`beforeLoad\` option
@@ -1909,7 +1912,7 @@ TanStack Router is designed to run loaders in parallel and wait for all of them
 
 Deferred data loading is a pattern that allows the router to render the next location's critical data/markup while slower, non-critical route data is resolved in the background. This process works on both the client and server (via streaming) and is a great way to improve the perceived performance of your application.
 
-If you are using a library like [TanStack Query](https://react-query.tanstack.com) or any other data fetching library, then deferred data loading works a bit differently. Skip ahead to the [Deferred Data Loading with External Libraries](#deferred-data-loading-with-external-libraries) section for more information.
+If you are using a library like [TanStack Query](https://tanstack.com/query/latest) or any other data fetching library, then deferred data loading works a bit differently. Skip ahead to the [Deferred Data Loading with External Libraries](#deferred-data-loading-with-external-libraries) section for more information.
 
 ## Deferred Data Loading with \`Await\`
 
@@ -2178,7 +2181,7 @@ To do this, you must:
 
 \`\`\`tsx
 export const Route = createRootRoute({
-  scripts: [
+  scripts: () => [
     {
       children: 'console.log("Hello, world!")',
     },
@@ -2321,7 +2324,7 @@ export const Route = createFileRoute('/posts')({
 
 ### Error handling with TanStack Query
 
-When an error occurs while using \`suspense\` with \`Tanstack Query\`, you'll need to let queries know that you want to try again when re-rendering. This can be done by using the \`reset\` function provided by the \`useQueryErrorResetBoundary\` hook. We can invoke this function in an effect as soon as the error component mounts. This will make sure that the query is reset and will try to fetch data again when the route component is rendered again. This will also cover cases where users navigate away from our route instead of clicking the \`retry\` button.
+When an error occurs while using \`suspense\` with \`TanStack Query\`, you'll need to let queries know that you want to try again when re-rendering. This can be done by using the \`reset\` function provided by the \`useQueryErrorResetBoundary\` hook. We can invoke this function in an effect as soon as the error component mounts. This will make sure that the query is reset and will try to fetch data again when the route component is rendered again. This will also cover cases where users navigate away from our route instead of clicking the \`retry\` button.
 
 \`\`\`tsx
 export const Route = createFileRoute('/')({
@@ -3034,6 +3037,30 @@ const link = (
 
 As seen above, it's common to provide the \`route.fullPath\` as the \`from\` route path. This is because the \`route.fullPath\` is a reference that will update if you refactor your application. However, sometimes it's not possible to import the route directly, in which case it's fine to provide the route path directly as a string. It will still get type-checked as per usual!
 
+### Special relative paths: \`"."\` and \`".."\`
+
+Quite often you might want to reload the current location, for example, to rerun the loaders on the current and/or parent routes, or maybe there was a change in search parameters. This can be achieved by specifying a \`to\` route path of \`"."\` which will reload the current location. This is only applicable to the current location, and hence any \`from\` route path specified is ignored.
+
+Another common need is to navigate one route back relative to the current location or some other matched route in the current tree. By specifying a \`to\` route path of \`".."\` navigation will be resolved to either the first parent route preceding the current location or, if specified, preceding the \`"from"\` route path.
+
+\`\`\`tsx
+export const Route = createFileRoute('/posts/$postId')({
+  component: PostComponent,
+})
+
+function PostComponent() {
+  return (
+    <div>
+      <Link to=".">Reload the current route of /posts/$postId</Link>
+      <Link to="..">Navigate to /posts</Link>
+      <Link from="/posts" to="..">
+        Navigate to root
+      </Link>
+    </div>
+  )
+}
+\`\`\`
+
 ### Search Param Links
 
 Search params are a great way to provide additional context to a route. For example, you might want to provide a search query to a search page:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tanstack/react-router",
-  "version": "1.130.8",
+  "version": "1.130.10",
   "description": "Modern and scalable routing for React applications",
   "author": "Tanner Linsley",
   "license": "MIT",
@@ -80,7 +80,7 @@
     "tiny-invariant": "^1.3.3",
     "tiny-warning": "^1.0.3",
     "@tanstack/history": "1.129.7",
-    "@tanstack/router-core": "1.130.8"
+    "@tanstack/router-core": "1.130.10"
   },
   "devDependencies": {
     "@testing-library/jest-dom": "^6.6.3",