🛠️ create-zeapp

🚀 Quick start

npm create zeapp@latest myapp
cd myapp
npx zeapp serve --open

That scaffolds a bundler-free app with the house conventions baked in (DESIGN.md §2.4): boot-only app.js, one module per feature, vendored SDK, import map so import { createShell } from "zesdk" works straight in the browser, README + Keep-a-Changelog pre-filled, fr.makix.<name> identifier.

📦 Commands

| Command | Does | |---|---| | create-zeapp <name> | scaffold a new app (--title, --id, --git, --force; prompts when run bare) | | zeapp serve [dir] | zero-dep static dev server (--port 4600, --open) | | zeapp view <name> | generate src/modules/<name>.js and register it in app.js (--title, --icon) | | zeapp icons [filter] | list the zesdk icon names | | zeapp update | re-vendor the newest reachable zesdk into src/vendor/zesdk | | zeapp help / version | usage / version |

create-zeapp and zeapp are the same binary — use whichever reads better.

🧭 How the pieces fit

• Scaffold — copies templates/app/, substitutes {{name}}/{{title}}/{{id}}, and vendors the SDK (resolved from the app's node_modules, then this CLI's dependency, then the monorepo sibling).
• zeapp.json — tiny app manifest at the project root; it is how zeapp view and zeapp update find the app from any subdirectory.
• Markers — app.js carries // zeapp:module-imports and // zeapp:module-list comments; the view generator inserts above them, so registration stays automatic.
• Web now, desktop later — the served app uses the zesdk bridge's web mode; wiring Tauri (frontendDist: src/, withGlobalTauri) needs no frontend changes.