Add TanStack Start server code example for chat API

[harlley]

The Next.js-only code was confusing for a beginner unfamiliar with Tanstack syntax.

🎯 Changes

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested this code locally with pnpm run test:pr.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
• This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Documentation
  • Added a new TanStack Start example to the Quick Start that demonstrates a complete chat API endpoint with streaming responses and error handling.
  • Replaced the previous Next.js header with the new TanStack Start block and cleaned up the Next.js snippet to keep only the relevant imports.
  • Improved Quick Start guidance for implementing streaming chat endpoints.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated the quick-start documentation to add a complete TanStack Start server POST /api/chat example (with API key validation, request parsing, streaming response via chat(...).toStreamResponse, and error handling) and replaced Next.js placeholder comments with a concrete POST handler import snippet.

Changes

Cohort / File(s)	Summary
Quick-start documentation updates docs/getting-started/quick-start.md	Added a TanStack Start POST /api/chat API route example (OPENAI_API_KEY validation, parsing messages and conversationId, streaming chat via chat({ adapter: openai(), ... }), converting to HTTP stream with toStreamResponse, and JSON 500 error handling). Replaced Next.js placeholder header with remaining import statements.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Documentation-only change containing code examples.
• Reviewer should quickly verify example correctness and consistency of shown imports/endpoints.

Poem

🥕 A rabbit read the docs at night,
Tucked examples in with gentle bite,
TanStack streaming, Next.js neat,
API keys checked — the guide's complete,
Hop happy, code that hums just right.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: adding a TanStack Start server code example for the chat API endpoint.
Description check	✅ Passed	The description follows the template structure with completed checklist items and release impact marked appropriately, though the Changes section lacks details about what was added.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f07605b and 5a90539.

📒 Files selected for processing (1)

• docs/getting-started/quick-start.md (1 hunks)

🔇 Additional comments (3)

docs/getting-started/quick-start.md (3)

22-76: LGTM! TanStack Start example is complete and well-structured.

The new TanStack Start API route includes all necessary components:

• Proper framework integration with createFileRoute and server handlers
• API key validation with appropriate error responses
• Correct request parsing for messages and conversationId
• Streaming response setup using chat() and toStreamResponse()
• Comprehensive error handling with JSON responses

The example is consistent with the Next.js version below it and provides clear guidance for TanStack Start users.

---

22-122: Excellent documentation approach with dual examples.

Having both TanStack Start (lines 22-75) and Next.js (lines 77-122) examples side-by-side effectively addresses the PR objective. Both examples are logically equivalent and demonstrate the same best practices:

• Consistent error handling patterns
• Same validation and streaming logic
• Only differing in framework-specific syntax

This helps beginners unfamiliar with either framework understand the core concepts while seeing their preferred framework's implementation.

---

22-75: Hard tabs have been successfully removed from the TanStack Start code block.

The previous markdown linting violation (MD010) flagged at lines 30–73 has been resolved. All indentation now uses spaces.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 049eb8a and f07605b.

📒 Files selected for processing (1)

• docs/getting-started/quick-start.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

docs/getting-started/quick-start.md

30-30: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

31-31: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

32-32: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

33-33: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

34-34: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

35-35: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

36-36: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

37-37: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

38-38: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

39-39: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

40-40: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

41-41: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

42-42: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

43-43: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

44-44: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

46-46: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

48-48: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

49-49: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

50-50: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

51-51: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

52-52: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

53-53: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

54-54: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

55-55: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

57-57: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

58-58: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

59-59: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

60-60: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

61-61: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

62-62: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

63-63: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

64-64: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

65-65: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

66-66: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

67-67: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

68-68: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

69-69: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

70-70: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

71-71: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

72-72: Hard tabs
Column: 1

(MD010, no-hard-tabs)

---

73-73: Hard tabs
Column: 1

(MD010, no-hard-tabs)

🔇 Additional comments (1)

docs/getting-started/quick-start.md (1)

22-122: Well-structured examples demonstrating equivalent functionality across frameworks.

The addition of the TanStack Start example alongside the Next.js implementation is excellent for documentation clarity. Both examples properly demonstrate:

• Environment variable validation
• Request parsing with conversationId and messages
• Streaming chat response creation via the chat() API
• Proper error handling with JSON error responses

The parallel structure makes it easy for developers familiar with either framework to understand how to implement the same functionality.