With file-system routing, Server Components, streaming, and caching.
$ pnpm create rebask-appStatic shell, served from cacheStreamed per request
Routing, rendering, and caching work together, partial prerendering by default.
Components run on the server by default and fetch their own data. Add "use client" where you need state, and only those components ship JavaScript.
Pages, layouts, and route handlers are files in app/. Nest layouts and use dynamic segments, catch-alls, and route groups.
Routes are prerendered into cached shells. A request gets the shell at once while its dynamic parts stream in.
Soft navigations fetch only missing segments. Links prefetch the shell in view and the full payload on hover.
From page shells and data on the server to route segments in the browser. Each layer has its own lifetime and tags.
A page in production, from the first byte to the next click.
One command scaffolds a Vite app with a root layout and your first pages.
$ pnpm create rebask-app