MODELDRIFT.WATCH

Sep 26 · Day 17

MINOR · CLAUDE · QUESTION 31

Claude changed its list for a question about which JavaScript framework to start with.

Why it’s minor

Which products a model recommends is read out of its answer by the least reliable part of our scorer, so compare the two answers before reading much into this.

The full answers

Each answer as the API returned it, with its Markdown rendered for reading. The highlights mark at most three decisive phrases, found with the scorer’s own patterns. Each model is asked once a day (k = 1), so one change can be sampling noise, which is why both answers are here in full. How scoring works.

Asked verbatim · Question 31

Which JavaScript framework should I start a new project with today?

SEP 25beforePermalink

Picks read from the answer, in order
  1. React + Vite
  2. Astro
  3. Next.js
  4. Angular
  5. Tiebreakers

Short answer: React + Vite if you want the safest bet, or SvelteKit / Nuxt if you're a small team optimizing for how fast and pleasant the work actually is.

Longer answer, because the right pick genuinely depends on a few things:

By project type

  • •Content-heavy site (marketing, docs, blog, e-commerce catalog) → Astro. Ships almost no JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them.
  • •SPA / internal dashboard / behind a login → Vite + React (or Vue, or Svelte). You don't need a meta-framework. SEO doesn't matter, so skip the SSR complexity entirely. This is the most underrated option — a lot of people reach for Next.js and inherit a pile of server/client boundary problems they never needed.
  • •Public-facing app that needs SSR and SEO → Next.js (React), Nuxt (Vue), or SvelteKit (Svelte). All three are solid. Next.js has the biggest ecosystem and the most churn; Nuxt and SvelteKit are calmer.
  • •Large enterprise team, want strong conventions → Angular. Its reputation lags its current state — signals and standalone components modernized it substantially. Batteries-included, opinionated, good when you have many developers who need guardrails.

Tiebreakers

  • •Hiring, contractors, or needing Stack Overflow answers to exist → React. It's not the best framework, it's the one with the deepest gravity well.
  • •Small team, you control the stack, you value DX → Svelte 5 or Vue 3. Both have meaningfully less ceremony than React. Svelte's runes and Vue's composition API are, in my view, nicer reactivity models than hooks.
  • •Team already knows one of these → use that. This dominates almost every other consideration. Framework choice is rarely the thing that sinks a project.

What I'd want to know to be more useful: Is it public or behind auth? Solo or team? Do you need SEO? Where are you deploying (Vercel/Cloudflare/your own box)? Any existing stack to fit into?

One caveat: my knowledge has a cutoff, and this ecosystem moves fast — there may be newer releases or shifts I'm not aware of. The structural advice above should hold up, but check current versions and release notes before committing.

SEP 26afterPermalink

Picks read from the answer, in order
  1. React with Vite
  2. Astro
  3. Next.js
  4. Angular
  5. Svelte

Short answer: if you have no strong constraints, React with Vite for an app behind a login, or Next.js if you need SSR/SEO. React remains the safest default because of ecosystem depth, hiring, and the sheer volume of examples (including what AI tools generate well).

But the honest answer depends on what you're building:

Content-heavy site (marketing, blog, docs) → Astro. Ships almost no JS by default, and you can drop in React/Vue/Svelte components where you need interactivity.

Full-stack app needing SSR/SEO → Next.js (React), Nuxt (Vue), or SvelteKit. Next has the biggest ecosystem but also the most complexity — the App Router, Server Components, and caching model take real effort to learn. Nuxt and SvelteKit are noticeably more pleasant if you don't need React specifically.

Internal dashboard / SPA with no SEO needs → Vite + React (or Vue), plus TanStack Query and TanStack Router. This is underrated. Skipping a meta-framework removes a lot of accidental complexity when you don't need server rendering.

Large team, long-lived enterprise project → Angular is a reasonable choice despite the reputation. It's opinionated, batteries-included, and its recent signals-based reactivity is good. Fewer "which library do we pick for X" debates.

Mobile app too → learn React, so you can share concepts with React Native/Expo.

Solo project, you care about DX and bundle size → Svelte. It's genuinely the most enjoyable of the bunch for many people; the tradeoff is a smaller library ecosystem.

Two caveats worth flagging:

  • 1.Framework choice matters less than you think. Your data layer, auth, and deployment story will cause more pain than your view library. Don't spend a week deciding.
  • 2.My information has a cutoff, and this space moves fast — check current versions and release notes before committing. TanStack Start in particular was maturing quickly and may be worth a look now.

What are you building? If you tell me the type of app, team size, and whether you need SEO, I can give you a more specific recommendation.

Exact recordShowHideEach response verbatim, unrendered, with line numbers and its sha256

Before baseline

2026-09-25 permalink

Scored
answered
Received
2026-09-25 09:23:04 UTC
Run
20260925T090007Z-f08d1f
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,247 characters · 1,974 tokens out incl. hidden reasoning · 30.2 s
Extracted picks, in order · confidence medium
  1. React + Vite
  2. Astro
  3. Next.js
  4. Angular
  5. Tiebreakers

Highlighted: the names the extractor took as picks, where they appear verbatim (5 of 5).

Short answer: **React + Vite** if you want the safest bet, or **SvelteKit / Nuxt** if you're a small team optimizing for how fast and pleasant the work actually is.
Longer answer, because the right pick genuinely depends on a few things:
**By project type**
- **Content-heavy site** (marketing, docs, blog, e-commerce catalog) → **Astro**. Ships almost no JS by default, and you can drop in React/Vue/Svelte components as interactive islands where you actually need them.
- **SPA / internal dashboard / behind a login** → **Vite + React** (or Vue, or Svelte). You don't need a meta-framework. SEO doesn't matter, so skip the SSR complexity entirely. This is the most underrated option — a lot of people reach for Next.js and inherit a pile of server/client boundary problems they never needed.
- **Public-facing app that needs SSR and SEO** → **Next.js** (React), **Nuxt** (Vue), or **SvelteKit** (Svelte). All three are solid. Next.js has the biggest ecosystem and the most churn; Nuxt and SvelteKit are calmer.
- **Large enterprise team, want strong conventions** → **Angular**. Its reputation lags its current state — signals and standalone components modernized it substantially. Batteries-included, opinionated, good when you have many developers who need guardrails.
**Tiebreakers**
- *Hiring, contractors, or needing Stack Overflow answers to exist* → React. It's not the best framework, it's the one with the deepest gravity well.
- *Small team, you control the stack, you value DX* → Svelte 5 or Vue 3. Both have meaningfully less ceremony than React. Svelte's runes and Vue's composition API are, in my view, nicer reactivity models than hooks.
- *Team already knows one of these* → use that. This dominates almost every other consideration. Framework choice is rarely the thing that sinks a project.
**What I'd want to know to be more useful:** Is it public or behind auth? Solo or team? Do you need SEO? Where are you deploying (Vercel/Cloudflare/your own box)? Any existing stack to fit into?
One caveat: my knowledge has a cutoff, and this ecosystem moves fast — there may be newer releases or shifts I'm not aware of. The structural advice above should hold up, but check current versions and release notes before committing.

End of response · 20 lines · 2,247 characters · sha256 773666947628f31109a14221eafe185ed953336dee0b8bf97eb319f8d500d4e5

After this run

2026-09-26 permalink

Scored
answered
Received
2026-09-26 09:22:01 UTC
Run
20260926T090007Z-89c0b7
Served by
Claude Platform on AWS · HTTP 200 · finish stop
Size
2,110 characters · 1,798 tokens out incl. hidden reasoning · 26.2 s
Extracted picks, in order · confidence medium
  1. React with Vite
  2. Astro
  3. Next.js
  4. Angular
  5. Svelte

Highlighted: the names the extractor took as picks, where they appear verbatim (5 of 5).

Short answer: if you have no strong constraints, **React with Vite** for an app behind a login, or **Next.js** if you need SSR/SEO. React remains the safest default because of ecosystem depth, hiring, and the sheer volume of examples (including what AI tools generate well).
But the honest answer depends on what you're building:
**Content-heavy site** (marketing, blog, docs) → **Astro**. Ships almost no JS by default, and you can drop in React/Vue/Svelte components where you need interactivity.
**Full-stack app needing SSR/SEO** → **Next.js** (React), **Nuxt** (Vue), or **SvelteKit**. Next has the biggest ecosystem but also the most complexity — the App Router, Server Components, and caching model take real effort to learn. Nuxt and SvelteKit are noticeably more pleasant if you don't need React specifically.
**Internal dashboard / SPA with no SEO needs** → **Vite + React** (or Vue), plus TanStack Query and TanStack Router. This is underrated. Skipping a meta-framework removes a lot of accidental complexity when you don't need server rendering.
**Large team, long-lived enterprise project** → **Angular** is a reasonable choice despite the reputation. It's opinionated, batteries-included, and its recent signals-based reactivity is good. Fewer "which library do we pick for X" debates.
**Mobile app too** → learn **React**, so you can share concepts with React Native/Expo.
**Solo project, you care about DX and bundle size** → **Svelte**. It's genuinely the most enjoyable of the bunch for many people; the tradeoff is a smaller library ecosystem.
Two caveats worth flagging:
1. **Framework choice matters less than you think.** Your data layer, auth, and deployment story will cause more pain than your view library. Don't spend a week deciding.
2. My information has a cutoff, and this space moves fast — check current versions and release notes before committing. TanStack Start in particular was maturing quickly and may be worth a look now.
What are you building? If you tell me the type of app, team size, and whether you need SEO, I can give you a more specific recommendation.

End of response · 22 lines · 2,110 characters · sha256 5c1d6567fd7fc85f7d795403d6915fc366504a54179f2dadef2c26e532348e05

Record detailsShowHideModel version, runs, baseline, triage, permalink, event ID
Model
anthropic/claude-opus-5
pinned anthropic/claude-opus-5-20260723; alias resolved to anthropic/claude-opus-5-20260723 at 2026-09-26 09:00:06 UTC (matches the pin)
Prompt
Question 31: P26 (recommendation)
Why this question
Tools for building websites change fast, so the answer shows how current a model’s knowledge is.
Change
1 added, 1 dropped
Baseline
4 prior days with data; 1 matched the baseline value (2026-09-25)
Responses
before 2026-09-25 09:23:04 UTC, run 20260925T090007Z-f08d1f; after 2026-09-26 09:22:01 UTC, run 20260926T090007Z-89c0b7
Detected
2026-09-26 · run 20260926T090007Z-89c0b7, started 2026-09-26 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-09-26/P26/anthropic/claude-opus-5/pick_change/picks/
Event ID
2026-09-26:P26:anthropic/claude-opus-5:pick_change:picks

Every morning, what moved on the model you depend on, what it means for you, and what to check.

$9 a month. Cancel any time. The next one tomorrow morning.

Get the daily brief

$99 once, for as long as modeldrift.watch runs. The first 100 buyers.

The record stays free. The brief is the reading of it.