▲nextdoctor

Stop your Next.js dev server
from eating your RAM.

Diagnose, auto-fix, and watch memory usage of Next.js dev servers — free and open source.

$npx @gowhiteleaf/nextdoctor diagnose

No install required — try it on one project before deciding anything.

Read the docsView on GitHub
nextdoctor dev
nextdoctor dev — 2 appsuptime 12m 41s · ←/→ switch · r restart · q quit
▶ webrunning
2.1 GB (peak 2.4 GB)
▂▃▄▅▆▇█▇▆▅▄▃▂▃▄▅▆▇
pid 41213: 1.8 GB pid 41240: 210 MB pid 41244: 95 MB
adminrunning
340 MB (peak 410 MB)
▁▂▂▃▃▂▂▁▂▃
pid 41290: 340 MB

A live, full-screen terminal dashboard — per-app memory gauge, trend sparkline, and process breakdown.

diagnose

Read-only scan of your project — Next.js version, Turbopack eviction status, config tuning, monorepo detection. Zero risk, safe on any project.

$ nextdoctor diagnose

fix

Applies the safe fixes diagnose found — onDemandEntries tuning, removing a disabled eviction flag. Always backs up your config first and shows the diff before writing.

$ nextdoctor fix

dev

Wraps your real dev command and shows live memory for the whole process tree in a full-screen dashboard — one app or several, side by side.

$ nextdoctor dev

Why this exists

Turbopack (the default bundler since Next.js 15) caches every route you visit during a dev session in memory. Before Next.js 16.3, it never evicted anything — so memory climbs the longer you work. 16.3 added eviction, but plenty of projects are stuck on older versions, on webpack, or just want visibility into what's actually eating RAM. That's what nextdoctor gives you.