Installation
Prerequisites
Section titled “Prerequisites”- Node.js 22+ and a package manager: pnpm, npm, yarn, or bun. Flare detects whichever one you use to run its own CLI and scaffolds the app with that manager’s lockfile.
- A Cloudflare account — but not yet. You don’t need one to scaffold an
app or run it locally.
flare devandflare startsimulate D1, R2, and KV locally through Wrangler. You only needwrangler loginwhen you’re ready to runflare deploy.
Run the CLI from this repo (for now)
Section titled “Run the CLI from this repo (for now)”git clone https://github.com/MUKE-coder/flare-framework.gitcd flare-frameworkpnpm installpnpm build # builds @flare/core and @flare/clinode packages/cli/bin/flare.js create ../myappWhen the CLI runs from a checkout, flare create points the new app’s
@flare/core and @flare/cli dependencies at the local packages (a
link:/file: path, or workspace:* if the app is inside the repo’s
workspace), so inside the app npx flare ... works as documented.
Install the CLI
Section titled “Install the CLI”npm install --save-dev @flare/cliYou don’t have to install it globally. flare create scaffolds a new app
that adds @flare/cli as a dev dependency automatically, so every command
after that runs through your package manager:
npx flare gen resource Contact --fields "name:string, email:string"# or, with pnpmpnpm flare gen resource Contact --fields "name:string, email:string"For the very first command — scaffolding the app itself — run the CLI directly with your package manager’s one-off runner:
npx @flare/cli create myapp# orpnpm dlx @flare/cli create myappVerify it worked
Section titled “Verify it worked”cd myappnpm run devThis starts vinext dev. Open the printed local URL — you should see the
scaffolded app’s home page, with sign-up and sign-in already wired to
Better Auth over a local D1 database. No Cloudflare login, no configuration.
Next: the five-minute quickstart.