nextrs docs
Everything to go from zero to a deployed Rust + React app. The same markdown that renders these pages also generates llms.txt and llms-full.txt, so the human docs and the LLM docs can't drift apart.
Guides
Getting Started
Create a React-first nextrs app and learn where application and generated code belong
Routing Conventions
Exact route filenames, free colocation, dynamic URLs, APIs, and server prefetch
A Rust-First Tour
Build from a tiny React component to local state, a typed Rust API call, React Query, and server-seeded data
Loading and Prefetch
Keep React navigation responsive while route code and server data are prepared
API Routes
Handler return shapes: bodies, status codes, headers, and typed errors
React Pages & Server Prefetch
page.tsx in the app tree, with the React Query cache warmed by the server before your bundle runs
Porting an Existing App
Start from the scaffold, graft your code into it, and convert route-by-route — the paved road for bringing an existing app to nextrs
List State Belongs in the URL
The default pattern for filters and pagination: URL search params, passed to the server, via the generated FromUrl hooks
Route Telemetry
Diagnose slow routes progressively: Server-Timing in DevTools, custom segments with the Timing extractor, and OpenTelemetry export for production history
Performance
Same app, same UI, same database — measured head to head, twice: a minimal app and a real production app converted end-to-end
nextrs.toml
The app's single config source for identity and deployment settings
Deploy: Build Locally, Ship Artifacts
Run the complete Vercel build locally, verify the Rust function exists, and upload prebuilt output
Cron Jobs
Declare schedules on protected Rust routes; nextrs generates the Vercel and Cloudflare trigger plumbing
Tooling Dependencies
The external tools a nextrs project uses, and which workflows need each one
Server Bundles
Give expensive routes their own Rust executable and deployed function using bundle.toml
FAQ
Short answers about NextRS development and deployment behavior
Client Generation
Deploy
Case studies
Case Study: Porting a 1.37M-LOC Next.js App
A 205-route production Next.js app ported to nextrs — every dev-loop dimension measured, honestly, including the two Next still wins
Case Study: A Production Booking App in 6 Hours
A real gym-management app — Next.js to nextrs at full behavioral parity in one evening, then measured on every dimension