Frontend framework
What this layer solves
The frontend is what runs in the browser: UI, navigation, fetching data. A modern framework gives you components, routing, and often API routes so you aren’t wiring everything by hand.
Options
| Framework | Best for | Tradeoffs |
|---|---|---|
| Next.js (React) | Full-stack JS/TS, SSR/SSG, huge ecosystem, Vercel integration | Opinionated; learn App Router mental model |
| Remix (React) | Web standards, forms, loaders | Smaller ecosystem than Next for some patterns |
| SvelteKit | Less JS shipped, lovely DX | Fewer Stack Overflow answers than React |
| Nuxt (Vue) | Vue teams | Different hiring/docs pool |
| Astro | Content-heavy sites + islands | Less default “full app” story than Next |
NK Wiki default: Next.js (App Router) — matches most AI-generated examples and Vercel deploys.
Outline: starting a Next app
- Node.js LTS installed — from nodejs.org .
npx create-next-app@latest— follow prompts (TypeScript, ESLint, Tailwind, App Router).- Read routing and server vs client components in current Next docs — this changes by major version.
- Add environment variables pattern early (
.env.local, never commit secrets).
Official links
When to pick an alternative
- SvelteKit if bundle size and simplicity beat ecosystem size for you.
- Remix if you want maximal control over forms and HTTP semantics.
Last reviewed: April 2026.
Last updated on