VRDexServer-side Convex baseline

First server-side App Router read path.

This route demonstrates the baseline Next.js server-component pattern for Convex in VRDex: use fetchQuery for a server-only read, and keep useQuery for reactive client surfaces.

Back to homepage Convex server docs

Live result

Convex server read failed

Start pnpm dev:backend:local, confirm NEXT_PUBLIC_CONVEX_URL is available to the web app, and reload this page.

Pattern rule

Use fetchQuery: For server components, route handlers, and server actions that only need a server-side read.
Use useQuery: For reactive client components like the homepage runtime card that should update after first render.
Defer preloadQuery: Until a feature actually needs server-rendered first paint plus a hydrated reactive client handoff.