Skip to content

Commit 4f288bf

Browse files
authored
Docs(Router-SSR): Resolve typos (#5425)
resolve typos
1 parent 3097080 commit 4f288bf

File tree

1 file changed

+4
-4
lines changed
  • docs/router/framework/react/guide

1 file changed

+4
-4
lines changed

docs/router/framework/react/guide/ssr.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -70,9 +70,9 @@ declare module '@tanstack/react-router' {
7070

7171
### Rendering the Application on the Server
7272

73-
Now that you have a router instance that has loaded all of the critical data for the current URL, you can render your application on the server:
73+
Now that you have a router instance that has loaded all the critical data for the current URL, you can render your application on the server:
7474

75-
using `defaultRenderToString`
75+
using `defaultRenderHandler`
7676

7777
```tsx
7878
// src/entry-server.tsx
@@ -85,7 +85,7 @@ import { createRouter } from './router'
8585
export async function render({ request }: { request: Request }) {
8686
const handler = createRequestHandler({ request, createRouter })
8787

88-
return await handler(defaultRenderToString)
88+
return await handler(defaultRenderHandler)
8989
}
9090
```
9191

@@ -144,7 +144,7 @@ With this setup, your application will be rendered on the server and then hydrat
144144

145145
## Streaming SSR
146146

147-
Streaming SSR is the most modern flavor of SSR and is the process of continuously and incrementally sending HTML markup to the client as it is rendered on the server. This is slightly different from traditional SSR in concept because beyond being able to dehydrate and rehydrate a critical first paint, markup and data with less priority or slower response times can be streamed to the client after the initial render, but in the same request.
147+
Streaming SSR is the most modern flavor of SSR and is the process of continuously and incrementally sending HTML markup to the client as it is rendered on the server. This is slightly different from traditional SSR in concept because beyond being able to dehydrate and rehydrate a critical first paint, markup and data with lower priority or slower response times can be streamed to the client after the initial render, but in the same request.
148148

149149
This pattern can be useful for pages that have slow or high-latency data fetching requirements. For example, if you have a page that needs to fetch data from a third-party API, you can stream the critical initial markup and data to the client and then stream the less-critical third-party data to the client as it is resolved.
150150

0 commit comments

Comments
 (0)