You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/router/framework/react/api/router/NavigateOptionsType.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ The `NavigateOptions` object accepts the following properties:
50
50
- Optional
51
51
- Defaults to `false`.
52
52
- If `true`, navigation will be called using `document.startViewTransition()`.
53
-
- If [`ViewTransitionOptions`](../ViewTransitionOptionsType.md), route navigations will be called using `document.startViewTransition({update, types})` where `types` will be the strings array passed with `ViewTransitionOptions["types"]`. If the browser does not support viewTransition types, the navigation will fall back to normal `document.startTransition()`, same as if `true` was passed.
53
+
- If [`ViewTransitionOptions`](../ViewTransitionOptionsType.md), route navigations will be called using `document.startViewTransition({update, types})` where `types` will determine the strings array passed with `ViewTransitionOptions["types"]`. If the browser does not support viewTransition types, the navigation will fall back to normal `document.startTransition()`, same as if `true` was passed.
54
54
- If the browser does not support this api, this option will be ignored.
55
55
- See [MDN](https://developer.mozilla.org/en-US/docs/Web/API/Document/startViewTransition) for more information on how this function works.
56
56
- See [Google](https://developer.chrome.com/docs/web-platform/view-transitions/same-document#view-transition-types) for more information on viewTransition types
Copy file name to clipboardExpand all lines: docs/start/framework/react/guide/server-functions.md
+10-16Lines changed: 10 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -228,20 +228,18 @@ Cache server function results at build time for static generation. See [Static S
228
228
229
229
Handle request cancellation with `AbortSignal` for long-running operations.
230
230
231
-
### Function ID generation
231
+
### Function ID generation for production build
232
232
233
233
Server functions are addressed by a generated, stable function ID under the hood. These IDs are embedded into the client/SSR builds and used by the server to locate and import the correct module at runtime.
234
234
235
-
Defaults:
236
-
237
-
- In development, IDs are URL-safe strings derived from `${filename}--${functionName}` to aid debugging.
238
-
- In production, IDs are SHA256 hashes of the same seed to keep bundles compact and avoid leaking file paths.
239
-
- If two server functions end up with the same ID (including when using a custom generator), the system de-duplicates by appending an incrementing suffix like `_1`, `_2`, etc.
240
-
- IDs are stable for a given file/function tuple for the lifetime of the process (hot updates keep the same mapping).
235
+
By default, IDs are SHA256 hashes of the same seed to keep bundles compact and avoid leaking file paths.
236
+
If two server functions end up with the same ID (including when using a custom generator), the system de-duplicates by appending an incrementing suffix like `_1`, `_2`, etc.
241
237
242
238
Customization:
243
239
244
-
You can customize function ID generation by providing a `generateFunctionId` function when configuring the TanStack Start Vite plugin.
240
+
You can customize function ID generation for the production build by providing a `generateFunctionId` function when configuring the TanStack Start Vite plugin.
241
+
242
+
Prefer deterministic inputs (filename + functionName) so IDs remain stable between builds.
245
243
246
244
Please note that this customization is **experimental** und subject to change.
- Prefer deterministic inputs (filename + functionName) so IDs remain stable between builds.
276
-
- If you don’t want file paths in dev IDs, return a hash in all environments.
277
-
- Ensure the returned ID is **URL-safe**.
278
-
279
273
---
280
274
281
275
> **Note**: Server functions use a compilation process that extracts server code from client bundles while maintaining seamless calling patterns. On the client, calls become `fetch` requests to the server.
0 commit comments