Updated
Ship and run

Frontend Framework

Pick the full-stack framework your web app lives in — routing, data loading, server code and rendering — on top of a UI library.

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Trends

Astro gained the most ground in package downloads: +99% against the median npm package over a year.

Public counts each month: pull requests on GitHub, package downloads, stars, Product Hunt followers. They show direction, not market share.

ToolDownloadsStarsProduct Hunt
React168M/wk+6% vs npm★ 251k4k followers
Next.js56M/wk+10% vs npm★ 143k8.2k followers
React Router51.6M/wk−26% vs npm★ 56.6k—
Vue.js15.2M/wk−44% vs npm★ 54.6k563 followers
TanStack Start15M/wk65.3× vs npm*★ 15.2k—
Angular5.8M/wk−60% vs npm★ 101.1k87 followers
Svelte5.6M/wk−30% vs npm★ 88.4k471 followers
Astro5.5M/wk+99% vs npm★ 63.3k1.8k followers
SolidJS4.8M/wk+45% vs npm★ 36.1k9 followers
SvelteKit2.6M/wk+15% vs npm★ 20.9k—
Nuxt2M/wk−42% vs npm★ 60.9k155 followers
Gradio1.2M/wk★ 43.8k94 followers
Alpine.js677.9k/wk−36% vs npm★ 32k25 followers
htmx246.1k/wk−24% vs npm★ 49.6k33 followers
EleventyRenamed189.2k/wk−42% vs npm★ 20k198 followers
Lately in this group
  • Oct 19 · Adoption 1372 more makers' products found using Next.js (now 1731).
Everything that changed →

The real choice

Which full-stack framework, and so which UI library under it. The React frameworks (Next.js, React Router, TanStack Start) get the largest pool of components, examples and AI-agent familiarity; SvelteKit and Nuxt trade that for Svelte's or Vue's style; Astro is content-first and ships almost no JavaScript, but isn't built for app-heavy screens. A bare UI library on Vite is still enough for a single-page app behind a login. If your backend already renders HTML, htmx and Alpine.js add interactivity without a JavaScript framework, and if your app is a Python script or model, Streamlit or Gradio give it a UI with no frontend code at all.

Pick by situation

Tap the ones that are you — the tools that fit light up below.
  • Your app lives behind a login and doesn't need search trafficReact
  • Public pages need server rendering and you want server code in the same React projectNext.jsReact RouterTanStack Start
  • You already know Vue, or Svelte, and need server renderingNuxtSvelteKit
  • You're building a marketing site, docs or a blogAstro

Compare the tools

Grouped by the side of the choice they answer, not ranked. Open a row for when to use it, the trade-off and what makers say.

ToolBest for
UI library (with Vite)1
Reactlibrary · open source · free tierSingle-page apps built from React components, with the largest ecosystem of component libraries, examples and AI-generated code.235+1405 open source168M/wk+6% vs npm

Use it whenYour app lives behind a login and doesn't need server rendering, or you want to pick routing and data libraries yourself.

Trade-offOn its own it has no routing, data loading or server rendering; you assemble those from separate libraries or move to a React framework.

llms.txt

Used by 3D AI Studio, Airial Travel, Aritect, Bank Statement Converter, BasedLabs.ai and 230 more · in 1405 open-source projects.

Powers our frontend. It made building an intuitive and fast interface so much easier, and its huge ecosystem gave us the confidence to experiment without worrying about running into walls.
Incerto, the makerSep 2026 ↗
React full-stack3
Next.jsframework · open source · free tierReact apps that want server rendering, API routes and the largest set of examples, templates and SaaS starters.1731+364 open source56M/wk+10% vs npm

Use it whenYou want the most tutorials and boilerplates to lean on.

Trade-offServer components and caching rules add concepts to learn, and some features work most smoothly on Vercel.

llms.txtCLI

Used by 1752vc Pitch Deck Analyzer, AgentCenter for OpenClaw, Antispace, ArtMathCode, Automaticall and 1726 more · in 364 open-source projects.

Built the foundation for a lightning-fast product experience with modern full-stack capabilities. From performance to scalability, it helped us move from idea to execution rapidly.
Nautis, the makerSep 2026 ↗
React Routerframework · open source · free tierReact apps built around web standards — loaders, actions and forms — in the lineage of Remix.1+443 open source51.6M/wk−26% vs npm

Use it whenYou like explicit data loading per route and want to deploy on any Node or edge host.

Trade-offSmaller ecosystem of starters than Next.js, and the project has changed names and APIs over its history.

Used by Fuser · in 443 open-source projects.

TanStack Startframework · open source · free tierType-safe routing and server functions for React or Solid, built on TanStack Router.51 open source15M/wk65.3× vs npm*

Use it whenYou already use TanStack Query or Router and want end-to-end types.

Trade-offYounger than the alternatives, with fewer examples and hosting guides.

llms.txtCLI

No maker's product we track shows it for this yet · in 51 open-source projects.

Svelte or Vue full-stack2
Nuxtframework · open source · free tierVue apps, with a large module ecosystem for auth, content, images and SEO.28+49 open source2M/wk−42% vs npm

Use it whenYou already know Vue.

Trade-offSmaller ecosystem and fewer AI-generated examples than React.

llms.txtCLI

Used by Chat Thing, Melies, Octrafic, Waitlister, Adkit Studio and 23 more · in 49 open-source projects.

Powers octrafic.com. I needed a landing page that's fast, SEO-friendly, and looks professional - Nuxt delivered all three with minimal setup. From zero to production in a weekend.
Octrafic, the makerSep 2026 ↗
SvelteKitframework · open source · free tierApps written in Svelte, with less boilerplate and small client bundles.2+74 open source2.6M/wk+15% vs npm

Use it whenYou chose Svelte and need routing, server rendering or server code.

Trade-offFewer third-party component libraries than React.

llms.txtMCPCLI

Used by Startup Krea, Modal · in 74 open-source projects.

Content-first1
Astroframework · open source · free tierMarketing sites, docs and blogs that ship minimal JavaScript, with interactive islands from any UI library.270+80 open source5.5M/wk+99% vs npm

Use it whenMost pages are content and only a few parts need to be interactive.

Trade-offNot designed for app-like dashboards with lots of client-side state.

CLI

Used by Aritect, ASO, Baselight, Bolt, Chime and 265 more · in 80 open-source projects.

In ASO.dev, we love using Astro Starlight theme, it’s a fantastic choice, especially for building FAQ sections. If you’re looking to optimize your site’s performance while keeping things simple and flexible, it is a great fit!
ASO, the makerSep 2026 ↗

Who switches to what

Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes, by developers in general rather than makers only. Pick a flow to see its pull requests.

Next.js → Astro: 178 pull requestsReact → Astro: 123 pull requestsNext.js → TanStack Start: 92 pull requestsReact → Next.js: 73+ pull requestsReact Router → Next.js: 49 pull requestsAstro → Next.js: 48 pull requestsNext.js → React Router: 25 pull requestsNext.js → SvelteKit: 22 pull requestsNext.js 317React 196React Router 49Astro 48Astro 301Next.js 170TanStack Start 92React Router 25SvelteKit 22Moving fromMoving to
Next.js → Astro178 PRs · Compare →

What Hacker News says

Hacker News commenters choose React most often for frontend framework, and like Astro best (net praise +37%). Among products launched since 2024 that show their choice, 80% use Next.js.

ToolHN comments choosing itNet praise on HNMakers' launches since 2024
React2,219−10%7% 122
Next.js873−14%80% 1,324
Vue.js693+10%2% 37
htmx602+31%0% 3
Svelte527+27%2% 34
Astro309+37%9% 153
Angular247−14%0% 8
SvelteKit161+31%0% 0

Comments January 2023 to August 2026 that name the tool in a sentence like "I use" or "we moved to", estimated from a sample Claude read; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. Makers: of 1,656 launches that show what they use here. HN commenters and makers are different crowds — where they agree and where they split.

Before you choose

How to approach it

Pick the UI library you already know, then decide whether you need a framework around it. A dashboard or tool behind a login that doesn't need search traffic can be a UI library on Vite plus a separate API. Reach for a full-stack framework when public pages need server rendering or you want server code in the same project. For a marketing site or blog, use a content-first framework and keep the app separate if needed. Don't switch frameworks mid-build for performance — at solo scale, it is rarely the bottleneck.

Common mistakes
  • Server-rendering a dashboard behind a login that no search engine will ever see, adding server cost and complexity for nothing.
  • Building the marketing site and blog inside the logged-in app, so every landing-page tweak goes through the app's build and deploy.
  • Picking a less common framework and then finding that component libraries, auth SDKs and AI-generated code mostly assume React.

Other options

Real choices most makers here won't need to weigh.

Decided alongside

What the 2,015 makers' products here chose for their other decisions.

Further reading