Local development
Use the repository’s development container and package scripts as the starting point.
Requirements
The root manifest specifies Node 22.17.1 or later within 22.x, pnpm 10.x, and pins the package manager to 10.32.0. Recheck the manifest when changing revisions.
docker compose --profile dev up -d
docker compose exec devcontainer bashWorkspace installation is handled by the container setup. Run shared builds and Prisma migrations in the development container, not on the host. Do not repair a host native-dependency mismatch by reinstalling the entire workspace.
Workspace map
client/*, server/* and packages/* are pnpm workspaces. Shared modules live under packages/shared-*; Prisma lives under packages/database. Gno sources live under gno/contracts/r and gno/contracts/p.
Local endpoints
| Service | Host port |
|---|---|
| Game | 36036 |
| Docs development | 38083 |
| Bridge | 3020 |
| World | 3003 |
| Communicate | 3030 |
| Internal API | 3010 |
| Admin API / client | 3040 / 5173 |
| PostgreSQL / Redis | 5432 / 6379 |
| Gnoland RPC / Gnoweb | 26657 / 8888 |
compose.yaml owns service names and port mappings. These are local endpoints, not a public API promise. Use each package’s scripts for checks and read .env.example for configuration names; never publish credentials.
Docs
pnpm --filter docs dev
pnpm --filter docs buildThe production build exports static pages, indexes both languages and writes compatibility routes. See documentation maintenance.