moose-cli

CLI tool for Moose.

Installation

pnpm install

Development

# Run directly without building (recommended for development)
pnpm run dev hello

# Build the project (for production/releases)
pnpm run build

# Run the built CLI locally
pnpm start hello

Distribution

Option 1: npm (Recommended)

Publish to npm-regsitry and users can install globally:

npm publish
# Users then run:
npm install -g moose-cli
moose hello

Option 2: Standalone Binary Executables

Build standalone binaries that don't require Node.js to be installed:

# Build all platform binaries (Linux, macOS Intel/ARM, Windows)
pnpm run build:binaries

This creates platform-specific directories in dist/binaries/, each containing a moose executable:

• linux-x64/moose - Linux x64
• macos-x64/moose - macOS Intel
• macos-arm64/moose - macOS Apple Silicon
• win-x64/moose.exe - Windows x64

Testing the binary:

# On Linux/WSL:
./dist/binaries/linux-x64/moose hello

# On macOS:
./dist/binaries/macos-x64/moose hello
# or for Apple Silicon:
./dist/binaries/macos-arm64/moose hello

# On Windows:
dist\binaries\win-x64\moose.exe hello

Users can download the appropriate binary for their platform and run it directly without Node.js installed.

macOS Code Signing:

• If you build on macOS, binaries are automatically signed with an ad-hoc signature (sufficient for most internal use).
• If you build on Linux/Windows, you'll need to sign the macOS binaries separately on a Mac:

  codesign --sign - --force dist/binaries/macos-x64/moose
  codesign --sign - --force dist/binaries/macos-arm64/moose

• For public distribution, consider using a Developer ID certificate and notarization (see Apple's documentation).