CLI

The bext CLI scaffolds, runs, builds, and inspects PRISM apps. This page lists the commands used to develop an app; for the config they read, see the Config Reference.

Commands

Command What it does
bext new <name> --template <tpl> Scaffold a new app from a starter template.
bext dev Start the dev server with hot reload on http://127.0.0.1:3000.
bext build Build the production bundle into dist/.
bext run . Auto-detect, build, and serve in one command.
bext routes Print the discovered route tree.

bext new

Scaffold a new app from a starter:

bext new my-app --template @bext/starter-prism

Starter templates

Template For
@bext/starter-prism A PRISM app (the general starting point).
@bext/starter-blog A blog.
@bext/starter-docs A documentation site.
@bext/starter-saas A SaaS app.
@bext/starter-api An API-only app.

bext dev

Start the dev server with hot module reload. Defaults to http://127.0.0.1:3000.

bext dev
bext dev --port 4000
bext dev --listen 0.0.0.0:8080 --open
bext dev --no-hmr
Flag Effect
--port N Listen on port N (host stays 127.0.0.1).
--listen host:port Bind an explicit host and port.
--open Open the app in a browser on start.
--no-hmr Disable hot module reload.

bext build

Compile the app for production into dist/:

bext build

bext run

Auto-detect the app, build it, and serve it — a one-shot convenience over build + serve:

bext run .

bext routes

Print the route tree the app resolves. Add --json for machine-readable output:

bext routes
bext routes --json

Related