On this page

Installation

Cyberstrike can be installed through multiple package managers. Choose the method that best fits your development environment.

📸 SCREENSHOT: installation-terminal.png

Terminal installation output

npm (Recommended)

The recommended installation method for most users.

npm install -g cyberstrike

Verify the installation:

cyberstrike --version

Bun

For users preferring the Bun runtime:

# Install Bun if not already installed
curl -fsSL https://bun.sh/install | bash

# Install Cyberstrike
bun install -g cyberstrike

Homebrew (macOS)

For macOS users with Homebrew:

# Add the tap
brew tap cyberstrike-io/tap

# Install
brew install cyberstrike

curl (Linux/macOS)

Direct installation via shell script:

curl -fsSL https://cyberstrike.io/install.sh | bash

Caution

Always review installation scripts before executing them. The script source is available at github.com/CyberStrikeus/cyberstrike.io.

Docker

Run Cyberstrike in a containerized environment:

# Pull the image
docker pull cyberstrike/cyberstrike:latest

# Run interactively
docker run -it cyberstrike/cyberstrike

# Mount local directory
docker run -it -v $(pwd):/workspace cyberstrike/cyberstrike

Cargo (Rust)

For Rust developers:

cargo install cyberstrike

Verifying Installation

After installation, verify Cyberstrike is working:

# Check version
cyberstrike --version

# Run doctor to check system
cyberstrike doctor

Expected output:

cyberstrike 1.0.0
✓ Node.js 20.0.0
✓ Bun 1.1.0
✓ Git 2.40.0
✓ Configuration valid

Updating Cyberstrike

Update to the latest version:

# npm
npm update -g cyberstrike

# Bun
bun update -g cyberstrike

# Homebrew
brew upgrade cyberstrike

# Self-update
cyberstrike update

Uninstalling

Remove Cyberstrike from your system:

# npm
npm uninstall -g cyberstrike

# Bun
bun remove -g cyberstrike

# Homebrew
brew uninstall cyberstrike

Configuration files are stored in ~/.cyberstrike/ and can be removed manually if needed.

Troubleshooting

Command Not Found

If cyberstrike is not found after installation:

Check your PATH includes npm global bin directory
Restart your terminal
Run npm bin -g to find the global bin path

Permission Errors

On Linux/macOS, if you encounter permission errors:

# Fix npm permissions
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc

Version Conflicts

If you have multiple Node versions:

# Use nvm to manage versions
nvm use 20
npm install -g cyberstrike