This guide explains how to build distributable binaries for CodeNomad.
- Bun - Package manager and runtime
- Node.js - For electron-builder
- Electron Builder - Installed via devDependencies
All commands now run inside the workspace packages. From the repo root you can target the Electron app package directly:
npm run build --workspace @neuralnomads/codenomad-electron-appbun run build:binariesThis builds for macOS (Universal - Intel + Apple Silicon) by default.
# Universal (Intel + Apple Silicon) - Recommended
bun run build:mac
# Intel only (x64)
bun run build:mac-x64
# Apple Silicon only (ARM64)
bun run build:mac-arm64Output formats: .dmg, .zip
# x64 (64-bit Intel/AMD)
bun run build:win
# ARM64 (Windows on ARM)
bun run build:win-arm64Output formats: .exe (NSIS installer), .zip
# x64 (64-bit)
bun run build:linux
# ARM64
bun run build:linux-arm64Output formats: .AppImage, .deb, .tar.gz
bun run build:allThe build script performs these steps:
- Build @neuralnomads/codenomad → Produces the CLI
dist/bundle (also rebuilds the UI assets it serves) - Compile TypeScript + bundle with Vite → Electron main, preload, and renderer output in
dist/ - Package with electron-builder → Platform-specific binaries
Binaries are generated in the release/ directory:
release/
├── CodeNomad-0.1.0-mac-universal.dmg
├── CodeNomad-0.1.0-mac-universal.zip
├── CodeNomad-0.1.0-win-x64.exe
├── CodeNomad-0.1.0-linux-x64.AppImage
└── ...
CodeNomad-{version}-{os}-{arch}.{ext}
- version: From package.json (e.g.,
0.1.0) - os:
mac,win,linux - arch:
x64,arm64,universal - ext:
dmg,zip,exe,AppImage,deb,tar.gz
- Build on: macOS 10.13+
- Run on: macOS 10.13+
- Code signing: Optional (recommended for distribution)
- Build on: Windows 10+, macOS, or Linux
- Run on: Windows 10+
- Code signing: Optional (recommended for distribution)
- Build on: Any platform
- Run on: Ubuntu 18.04+, Debian 10+, Fedora 32+, Arch
- Dependencies: Varies by distro
# Install Xcode Command Line Tools
xcode-select --install# Install dependencies (Debian/Ubuntu)
sudo apt-get install -y rpm
# Install dependencies (Fedora)
sudo dnf install -y rpm-build# Install dependencies
bun install- Use platform-specific builds instead of
build:all - Close other applications to free up resources
- Use SSD for faster I/O
Development:
bun run dev # Hot reload, no packagingProduction:
bun run build:binaries # Full build + packagingExample GitHub Actions workflow:
name: Build Binaries
on:
push:
tags:
- "v*"
jobs:
build-mac:
runs-on: macos-latest
steps:
- uses: actions/checkout@v3
- uses: oven-sh/setup-bun@v1
- run: bun install
- run: bun run build:mac
build-win:
runs-on: windows-latest
steps:
- uses: actions/checkout@v3
- uses: oven-sh/setup-bun@v1
- run: bun install
- run: bun run build:win
build-linux:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: oven-sh/setup-bun@v1
- run: bun install
- run: bun run build:linuxEdit package.json → build section to customize:
- App icon
- Code signing
- Installer options
- File associations
- Auto-update settings
See electron-builder docs for details.
images/CodeNomad-Icon.png— primary asset for in-app logo placements and the 1024×1024 master icon used to generate packaged app icons
To update the binaries:
- Run
node scripts/generate-icons.js images/CodeNomad-Icon.png electron/resourcesto round the corners and emit freshicon.icns,icon.ico, andicon.pngfiles. - (Optional) Pass
--radiusto tweak the corner curvature or--nameto change the filename prefix. - If you prefer manual control, export
images/CodeNomad-Icon.pngwith your tool of choice and place the generated files inelectron/resources/.
Remove previous builds:
rm -rf release/ dist/
bun run build:binariesQ: Can I build for Windows on macOS?
A: Yes, but native binaries (e.g., DMG) require the target OS.
Q: How large are the binaries?
A: Approximately 100-150 MB (includes Electron runtime).
Q: Do I need code signing?
A: Not required, but recommended for public distribution to avoid security warnings.
Q: How do I update the version?
A: Update version in package.json, then rebuild.
For issues or questions:
- Check electron-builder documentation
- Open an issue in the repository
- Review existing build logs in
release/