Skip to content

Commit 664fe80

Browse files
ci: apply automated fixes
1 parent 40a260d commit 664fe80

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

src/blog/composite-components.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ React Server Components (RSC) are a genuine leap for React. They reduce bundle s
1313

1414
But existing implementations come with a tradeoff: the server owns the component tree. Your client code opts into interactivity with `'use client'`, and composition flows one direction: server decides, client receives.
1515

16-
What if RSCs were actually components that the client could fetch, cache, and compose on its own terms?
16+
What if RSCs were actually components that the client could fetch, cache, and compose on its own terms?
1717

1818
That's what we built in **TanStack Start**.
1919

@@ -347,8 +347,6 @@ RSC support is experimental in TanStack Start RC and will remain experimental in
347347
348348
**API surface:** The `createServerComponent` API and slot patterns are stable in design but may see refinements.
349349
350-
351-
352350
If you hit rough edges, [open an issue](https://github.com/tanstack/router/issues) or join the [Discord](https://tlinz.com/discord).
353351
354352
---

0 commit comments

Comments
 (0)