▲nextdoctor

Roadmap

nextdoctor started as a fix for one problem: Next.js dev servers eating gigabytes of RAM during local development. v1 (CLI: diagnose, fix, dev) covers that for a single project or a locally-run multi-app setup.

Where this goes next:

Near-term (v1.x, in the open now)

  • Harden fix across more next.config shapes (currently regex-based insertion — real-world testing across different projects will surface where this needs to get smarter)
  • Broader OS coverage/testing for the process-tree memory sampling (macOS confirmed; Linux/WSL need more real-world mileage)
  • More diagnose checks as they come up (source map settings, watched directory bloat, webpack vs Turbopack-specific advice)

v2 — connect multiple apps, not just multiple processes

Today's dev --config already runs several apps side by side in one dashboard. The next step is turning that into something you can use across projects and machines, not just multiple folders on one machine in one terminal session:

  • Persist memory history per app over time (not just the current session's peak) so you can see trends, not just a snapshot
  • Compare apps against each other — which of your projects is actually the memory hog, is it getting better or worse release over release
  • Surface this comparison somewhere outside the terminal dashboard so it's checkable without a dev session actively running

Later — a hosted layer (exploratory, not committed)

If there's real demand for the above beyond what a local file can hold: a lightweight opt-in hosted dashboard that aggregates stats across a person's or team's repos — history, comparisons, alerts. This would be a separate, clearly-optional product layered on top of the CLI, not a replacement for it. The CLI itself — diagnose, fix, and the local watchdog — stays free and open source regardless of whether this happens.

Not currently planned

  • Anything that requires telemetry or network calls by default
  • Vendor lock-in to a specific hosting provider for the core CLI

Have a request or a project that's breaking this in an interesting way? Open an issue — real-world usage across different codebases is what's shaping this roadmap.