ReferencePreview
npm scripts (IDE & desktop)
The scripts you'd actually run to develop, launch, or package the IDE.
AI
Preview — early access. This is a reference for people running the IDE from source, not the hosted Control Panel.
Overview
Most people use the hosted Control Panel and never touch these directly. This page is for anyone running the IDE from source or building the desktop installer themselves.
How it works
The web IDE and its Electron desktop wrapper are two npm projects: creytix-front (the Next.js app) and the desktop shell (a sibling package that bundles it into a native app).
Reference — creytix-front
| Script | What it does |
|---|---|
npm run dev | Starts the web IDE on port 3025 |
npm run start | Runs the production build on port 3025 |
npm run ide:desktop | Launches the Electron desktop shell against a running dev/start server |
Reference — desktop shell
| Script | What it does |
|---|---|
npm run dev | Launches Electron, which spawns a local Next.js server for the IDE |
npm run dist:mac | Builds macOS .dmg installers (arm64 + x64) into release/ |
npm run dist:win | Builds the Windows NSIS installer |
npm run dist | Builds for the current platform |
npm run publish:release | Uploads built installers + the update feed to the configured host |
npm run cask:build | Regenerates the Homebrew cask from the latest release/*.dmg |
npm run cask:sync | Mirrors the cask + README into a homebrew-tap checkout |
npm run serve:feed | Serves release/ locally over HTTP to test the auto-updater without a real host |
Limits & honest scope
- These scripts assume a local dev environment with
creytix-frontchecked out as a sibling directory — they aren't callable from the hosted Control Panel. dist:macproduces an unsigned build until Apple Developer ID credentials are supplied; see Install the desktop app.- Publishing installers requires update-host credentials (
CREYTIX_UPDATE_*env vars) that aren't documented here — they're operational secrets, not user-facing configuration.