# nextrs

> A Next.js-style routing framework for Rust built on Axum and Askama.


## Guides

- [Getting Started](https://nextrs-docs.vercel.app/docs/getting-started): Create a React-first nextrs app and learn where application and generated code belong
- [Routing Conventions](https://nextrs-docs.vercel.app/docs/conventions): Exact route filenames, free colocation, dynamic URLs, APIs, and server prefetch
- [A Rust-First Tour](https://nextrs-docs.vercel.app/docs/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](https://nextrs-docs.vercel.app/docs/streaming): Keep React navigation responsive while route code and server data are prepared
- [API Routes](https://nextrs-docs.vercel.app/docs/api-routes): Handler return shapes: bodies, status codes, headers, and typed errors
- [React Pages & Server Prefetch](https://nextrs-docs.vercel.app/docs/react-server-props): page.tsx in the app tree, with the React Query cache warmed by the server before your bundle runs
- [Porting an Existing App](https://nextrs-docs.vercel.app/docs/porting): 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](https://nextrs-docs.vercel.app/docs/url-state): The default pattern for filters and pagination: URL search params, passed to the server, via the generated FromUrl hooks
- [Route Telemetry](https://nextrs-docs.vercel.app/docs/telemetry): Diagnose slow routes progressively: Server-Timing in DevTools, custom segments with the Timing extractor, and OpenTelemetry export for production history
- [Performance](https://nextrs-docs.vercel.app/docs/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](https://nextrs-docs.vercel.app/docs/config): The app's single config source for identity and deployment settings
- [Deploy: Build Locally, Ship Artifacts](https://nextrs-docs.vercel.app/docs/deploy-prebuilt): Run the complete Vercel build locally, verify the Rust function exists, and upload prebuilt output
- [Cron Jobs](https://nextrs-docs.vercel.app/docs/crons): Declare schedules on protected Rust routes; nextrs generates the Vercel and Cloudflare trigger plumbing
- [Tooling Dependencies](https://nextrs-docs.vercel.app/docs/dependencies): The external tools a nextrs project uses, and which workflows need each one
- [Server Bundles](https://nextrs-docs.vercel.app/docs/server-bundles): Give expensive routes their own Rust executable and deployed function using bundle.toml
- [FAQ](https://nextrs-docs.vercel.app/docs/faq): Short answers about NextRS development and deployment behavior

## Client Generation

- [Generated TypeScript Client](https://nextrs-docs.vercel.app/docs/typesafe-client): How typed Rust routes become a linked fetch and React Query package with editor-ready declarations
- [Client Generation: Step by Step](https://nextrs-docs.vercel.app/docs/client-codegen): Turn typed Rust path, query, body, response, and error contracts into fetch functions and React Query hooks

## Deploy

- [Deploy to Vercel](https://nextrs-docs.vercel.app/docs/deploy-vercel): Run the shared Rust app as one Vercel function, regenerate frontend assets during the build, and preserve streaming
- [Deploy with Docker](https://nextrs-docs.vercel.app/docs/deploy-docker): Run a nextrs app on any container host — Fly.io, Railway, ECS, or a VPS

## Case studies

- [Case Study: Porting a 1.37M-LOC Next.js App](https://nextrs-docs.vercel.app/docs/case-study-port-at-scale): 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](https://nextrs-docs.vercel.app/docs/case-study-hhh): A real gym-management app — Next.js to nextrs at full behavioral parity in one evening, then measured on every dimension