FirebaseExtended / FirebaseExtended/reactfire
Spike: Next.js / React Server Components usage guide
- Langage dominant
- TypeScript
- Étoiles
- 3.6k
- Forks
- 403
- Merge moyen
- 14 h 53 min
- PR mergées (30 j)
- 5
Description
reactfire works with Next.js but the full SSR/RSC story needs exploration before we can write authoritative guidance. Known pieces:
**Solved (client-side patterns):**
- Context providers need `'use client'` for App Router
- Browser-only SDKs (Analytics, etc.) also need `ssr: false` via `next/dynamic` to prevent SSR initialization — see #530
**Needs exploration:**
- How to use Firestore with React Server Components, including serialization constraints (Firestore objects can't cross the RSC boundary as-is)
- Reference: https://firebase.blog/posts/2026/06/firestore-serialization-react
- General guidance for which reactfire hooks are RSC-compatible vs. client-only
Outcome: a "Using reactfire with Next.js / RSC" section in docs covering both the simple `'use client'` pattern and the Firestore SSR serialization approach.
Related: #530, #334
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Review related issues #530 and #334, then read the linked Firestore serialization reference. Explore Firestore use with React Server Components and determine which reactfire hooks are RSC-compatible versus client-only. Done means adding a “Using reactfire with Next.js / RSC” documentation section covering the 'use client' pattern and Firestore SSR serialization approach.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- firebase, next.js, react, typescript
- Domaine
- documentation, frontend
- Type d'issue
- Documentation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- Calme
- Clarté
- Plutôt claire
- Accessibilité débutants
- 38/100