Installation
stackr is run through npx — there is nothing to install globally. This page
covers the prerequisites for generating a project and booting it locally.
Prerequisites
| Requirement | Version | Needed for |
|---|---|---|
| Node.js | 22 or newer | Running the CLI and every service |
| A package manager | npm, yarn, or bun | Installing workspace dependencies |
| Docker | Recent | docker:dev and the test profiles |
| Git | Any | Version control (recommended) |
Docker is for running, not generating
The CLI itself does not require Docker. You only need it to bring the stack up
with docker:dev or to run the Docker-based test profiles. If you
prefer, you can run a single service against a host-mode database instead.
Node.js
stackr targets Node.js 22+ (its engines.node floor), and the generated
services are tested on the current LTS. Check your version:
node --versionPackage manager
npm, yarn, and bun are all first-class — you pick one during generation and every generated script branches on that choice. bun is the recommended default for its speed, but nothing in the generated project is bun-only.
Generating a project
Run the CLI with npx; it always uses the latest published version:
npx create-stackr@latest my-appThis launches the interactive wizard. To skip the prompts and generate the default
shape (Drizzle, an auth service with admin dashboard, and one core base service),
pass --defaults:
npx create-stackr@latest my-app --defaultsTwo binaries
The package ships two commands: create-stackr generates a new
project, and stackr operates inside an existing one
(adding services, adding entities, checking for drift). See the
CLI Reference.
Next steps
Head to the Quick Start to install dependencies, boot the stack, and run the tests — or jump to Configuration to walk through every option the wizard asks about.