MODELDRIFT.WATCH

Oct 1 · Day 22

MINOR · GPT · QUESTION 31

GPT went back to its earlier list for a question about which JavaScript framework to start with.

Why it’s minor

The change lasted one day before the model went back.

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 30the changePermalink

Picks read from the answer, in order
  1. React + TypeScript
  2. Next.js
  3. Vite

Default recommendation: start with React + TypeScript, using:

  • •Next.js for a full-stack app, public website, SEO, server rendering, or API routes.
  • •Vite for a client-only SPA or when the backend is separate.

Choose something else when priorities differ:

  • •Vue + Nuxt: easier learning curve and excellent conventions.
  • •Svelte + SvelteKit: minimal boilerplate and a highly productive developer experience.
  • •Angular: large enterprise teams needing strict structure and long-term consistency.
  • •Astro: content-heavy sites where minimal client-side JavaScript matters.

If I had no other project details, I’d choose Next.js with TypeScript, while avoiding unnecessary server components or complex caching until the app actually needs them. For a simple dashboard backed by an existing API, I’d choose React + Vite instead.

OCT 1backPermalink

Picks read from the answer, in order
  1. Next.js with TypeScript
  2. SvelteKit
  3. Nuxt
  4. Angular
  5. Astro
  6. Vite + React/Vue/Svelte

Default recommendation: Next.js with TypeScript.

Choose it when you’re building a production web app and want a large ecosystem, straightforward deployment, server rendering, API routes, and strong hiring/community support.

Use something else when your priorities differ:

  • •SvelteKit — simplest, most enjoyable option for a small team or greenfield product.
  • •Nuxt — best if your team prefers Vue.
  • •Angular — strong choice for large, structured enterprise teams.
  • •Astro — content-heavy sites, documentation, blogs, or marketing pages with minimal JavaScript.
  • •Vite + React/Vue/Svelte — client-only SPA that doesn’t need SSR or a full-stack framework.

My practical starting stack would be:

Next.js + TypeScript + PostgreSQL

Use the current stable Node.js LTS, keep dependencies minimal, and only add state-management libraries if you actually need them. If developer simplicity matters more than ecosystem size, pick SvelteKit instead.

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

Deviation the day it changed

2026-09-30 permalink

Scored
answered
Received
2026-09-30 09:21:19 UTC
Run
20260930T090007Z-45ce12
Served by
OpenAI · HTTP 200 · finish stop
Size
864 characters · 268 tokens out incl. hidden reasoning · 4.5 s
Extracted picks, in order · confidence medium
  1. React + TypeScript
  2. Next.js
  3. Vite

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

**Default recommendation:** start with **React + TypeScript**, using:
- **Next.js** for a full-stack app, public website, SEO, server rendering, or API routes.
- **Vite** for a client-only SPA or when the backend is separate.
Choose something else when priorities differ:
- **Vue + Nuxt:** easier learning curve and excellent conventions.
- **Svelte + SvelteKit:** minimal boilerplate and a highly productive developer experience.
- **Angular:** large enterprise teams needing strict structure and long-term consistency.
- **Astro:** content-heavy sites where minimal client-side JavaScript matters.
If I had no other project details, I’d choose **Next.js with TypeScript**, while avoiding unnecessary server components or complex caching until the app actually needs them. For a simple dashboard backed by an existing API, I’d choose **React + Vite** instead.

End of response · 13 lines · 864 characters · sha256 a115648e54922f6d93a5f0425dbd82cb9ca2d2587ce5d30e857b0c2b70e00cc2

Reverted back to baseline

2026-10-01 permalink

Scored
answered
Received
2026-10-01 09:22:25 UTC
Run
20261001T090007Z-857bc9
Served by
OpenAI · HTTP 200 · finish stop
Size
983 characters · 392 tokens out incl. hidden reasoning · 7.2 s
Extracted picks, in order · confidence medium
  1. Next.js with TypeScript
  2. SvelteKit
  3. Nuxt
  4. Angular
  5. Astro
  6. Vite + React/Vue/Svelte

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

**Default recommendation: Next.js with TypeScript**.
Choose it when you’re building a production web app and want a large ecosystem, straightforward deployment, server rendering, API routes, and strong hiring/community support.
Use something else when your priorities differ:
- **SvelteKit** — simplest, most enjoyable option for a small team or greenfield product.
- **Nuxt** — best if your team prefers Vue.
- **Angular** — strong choice for large, structured enterprise teams.
- **Astro** — content-heavy sites, documentation, blogs, or marketing pages with minimal JavaScript.
- **Vite + React/Vue/Svelte** — client-only SPA that doesn’t need SSR or a full-stack framework.
My practical starting stack would be:
```text
Next.js + TypeScript + PostgreSQL
```
Use the current stable Node.js LTS, keep dependencies minimal, and only add state-management libraries if you actually need them. If developer simplicity matters more than ecosystem size, pick **SvelteKit** instead.

End of response · 19 lines · 983 characters · sha256 4f7329457ce39a35817b1ae8411650cae2183d030a8a201e4c9098ee4a43010b

Record detailsShowHideModel version, runs, baseline, triage, permalink, event ID
Model
openai/gpt-5.6-sol
pinned openai/gpt-5.6-sol-20260709; alias resolved to openai/gpt-5.6-sol-20260709 at 2026-10-01 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
first extracted pick differs from the baseline's (full lists below)
Baseline
6 prior days with data; 5 matched the baseline value (2026-09-23, 2026-09-26, 2026-09-27, 2026-09-29, 2026-09-30)
Responses
deviation 2026-09-30 09:21:19 UTC, run 20260930T090007Z-45ce12; reverted 2026-10-01 09:22:25 UTC, run 20261001T090007Z-857bc9
Detected
2026-10-01 · run 20261001T090007Z-857bc9, started 2026-10-01 09:00:07 UTC · scorer v1 · severity rules r2
Permalink
https://modeldrift.watch/e/2026-10-01/P26/openai/gpt-5.6-sol/transient_anomaly/picks.top/
Event ID
2026-10-01:P26:openai/gpt-5.6-sol:transient_anomaly:picks.top

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.