Overview
The Komerza CLI lets you develop storefronts locally instead of inside the browser-based Builder. It keeps your local files in sync with your Builder project in real time, and lets you deploy directly to production from the terminal. The typical workflow is: clone → dev → deploy.Installation
komerza command is available globally.
Authentication
Login
Logout
Check who you’re logged in as
Cloning a Project
- A directory named after your project
- A
.komerza/config.jsonfile tracking the project - commit this file - A
.gitignore
Local Development
- Detects your package manager (
npm,pnpm,yarn, orbun) automatically - Requires a
"dev"script inpackage.json
The dev server and file-watching run together in the same terminal process.
Stop the server (Ctrl+C) to exit both.
Deploying
- Runs your
buildscript frompackage.json - Finds the build output (
dist,out,build,.next/out, orpublic/dist) - Uploads it and makes it live
Environment Variables
Manage env vars stored on your Builder project.Other Commands
Manual sync
dev and deploy.
komerza pull will ask for confirmation if local files already exist. Use -f / --force to skip the prompt.
List projects
Open in browser
Config File
.komerza/config.json is created when you run komerza clone. It stores:
Commit this file - it is required by most CLI commands.