absolute doctor

One command to answer “why won’t it start?” — a health check of your project and environment.

#Usage

Run absolute doctor from your project root. Each check is green (ok), yellow (warning), or red (failure); the command exits non-zero if anything fails, so it doubles as a CI gate. --fix repairs the safe issues automatically — creating any missing framework directories and scaffolding unset getEnv() keys into .env.example (placeholders only, never invented secrets). --json emits the checks for scripting.

BASH

# Diagnose the project (bun, config, framework dirs, env, dev port)
absolute doctor

# Auto-fix safe issues: create missing framework dirs, scaffold .env.example
absolute doctor --fix

# Machine-readable, exits non-zero on failures (for CI)
absolute doctor --json

#What it checks

The Bun runtime, that @absolutejs/absolute and the platform native binary resolve, that absolute.config.ts loads, that each configured framework’s pages directory exists, that every getEnv() variable is set, and whether the dev port is free.

absolute doctor

$ absolute doctor
  ✓ Bun runtime           v1.3.14
  ✓ @absolutejs/absolute  v0.19.0-beta
  ✓ Native binary         v0.19.0-beta
  ✓ Config                absolute.config.ts loaded
  ✓ react pages           ./src/frontend/react
  ✓ vue pages             ./src/frontend/vue
  ✗ Env vars              missing DATABASE_URL
  ⚠ Dev port              3000 in use by pid 48210

  8 checks · 1 failed · 1 warning

PreviousIslands NextEnv