Errors
When the CLI stops, it prints the address of the page that explains why. These are those pages: one problem each, the fix first, the reasoning underneath.
To check for all of them at once, before you start:
Terminal
$grit doctor --env
- A port the project needs is already takenUsually a server from an earlier run whose terminal was closed./e/port-in-use
- Docker is not runningThe daemon did not answer, which usually means Docker Desktop is closed./e/docker-not-running
- go: command not foundGo is not installed, or is installed and not on PATH./e/go-not-found
- Your Go is older than Grit needsOlder patches carry standard-library vulnerabilities a project reaches./e/go-too-old
- node: command not foundThe frontends need Node. An API-only project does not./e/node-not-found
- Your Node is older than the frontend needsNext declares a floor, and an old Node fails at build rather than at install./e/node-too-old
- pnpm: command not foundGenerated projects are a pnpm workspace, so npm produces a broken tree./e/pnpm-not-found
- This is not a Grit projectNo grit.json here or in any directory above./e/not-a-grit-project
A message not listed here is worth reading about in the errors guide, which covers every message a Go, Docker and Node project produces in its first hour, or in the troubleshooting page, which is about Grit specifically.
