LocalStage

LocalStage is a local development server and CLI for Basker themes. Run a theme locally while using live data from a Basker CMS environment.

Install

npm install -g @baskerhq/localstage

Usage

From a theme directory:

basker theme dev

Use a custom CMS URL:

BASKER_URL=https://example.com LOCALSTAGE_THEME_PATH=/path/to/theme basker theme dev

Open http://localhost:9292 and sign in.

Theme Structure

your_theme/
├── layouts/
│   └── default.liquid
├── templates/
│   ├── page.liquid
│   ├── post.liquid
│   └── 404.liquid
├── snippets/
└── assets/

Environment Variables

• BASKER_URL — CMS base URL
• LOCALSTAGE_THEME_PATH — path to a theme directory

Commands

Authentication

• basker auth login [theme-path] — authenticate and select a workspace
• basker auth tenant [theme-path] — switch the active workspace for this theme
• basker auth logout [theme-path] — clear the stored session for this theme

Theme

• basker theme dev [theme-path] — start the local dev server (alias: basker dev)
• basker theme check [theme-path] — validate theme structure and schema (alias: basker check)
• basker theme set [theme-path] --theme-id <id> — store or look up the theme ID used for remote settings

Common flags: --theme, -t <path>, --payload-url <url>, --port, -p <port> (dev only), --no-livereload (dev only), --debug, -d (dev only).

Troubleshooting

• Ensure your CMS URL is reachable and your account can access the target tenant.
• Verify the theme path exists and contains layouts/ and templates/.
• If sign-in fails, run basker auth logout then basker auth login to reset the cached session.