fluffbuzz.com.
Quick commands
- install.sh
- install-cli.sh
- install.ps1
If install succeeds but
fluffbuzz is not found in a new terminal, see Node.js troubleshooting.install.sh
Flow (install.sh)
1
Detect OS
Supports macOS and Linux (including WSL). If macOS is detected, installs Homebrew if missing.
2
Ensure Node.js 24 by default
Checks Node version and installs Node 24 if needed (Homebrew on macOS, NodeSource setup scripts on Linux apt/dnf/yum). FluffBuzz still supports Node 22 LTS, currently
22.14+, for compatibility.3
Ensure Git
Installs Git if missing.
4
Install FluffBuzz
npmmethod (default): global npm installgitmethod: clone/update repo, install deps with pnpm, build, then install wrapper at~/.local/bin/fluffbuzz
5
Post-install tasks
- Refreshes a loaded gateway service best-effort (
fluffbuzz gateway install --force, then restart) - Runs
fluffbuzz doctor --non-interactiveon upgrades and git installs (best effort) - Attempts onboarding when appropriate (TTY available, onboarding not disabled, and bootstrap/config checks pass)
- Defaults
SHARP_IGNORE_GLOBAL_LIBVIPS=1
Source checkout detection
If run inside an FluffBuzz checkout (package.json + pnpm-workspace.yaml), the script offers:
- use checkout (
git), or - use global install (
npm)
npm and warns.
The script exits with code 2 for invalid method selection or invalid --install-method values.
Examples (install.sh)
- Default
- Skip onboarding
- Git install
- GitHub main via npm
- Dry run
Flags reference
Flags reference
Environment variables reference
Environment variables reference
install-cli.sh
Designed for environments where you want everything under a local prefix
(default
~/.fluffbuzz) and no system Node dependency. Supports npm installs
by default, plus git-checkout installs under the same prefix flow.Flow (install-cli.sh)
1
Install local Node runtime
Downloads a pinned supported Node LTS tarball (the version is embedded in the script and updated independently) to
<prefix>/tools/node-v<version> and verifies SHA-256.2
Ensure Git
If Git is missing, attempts install via apt/dnf/yum on Linux or Homebrew on macOS.
3
Install FluffBuzz under prefix
npmmethod (default): installs under the prefix with npm, then writes wrapper to<prefix>/bin/fluffbuzzgitmethod: clones/updates a checkout (default~/fluffbuzz) and still writes the wrapper to<prefix>/bin/fluffbuzz
4
Refresh loaded gateway service
If a gateway service is already loaded from that same prefix, the script runs
fluffbuzz gateway install --force, then fluffbuzz gateway restart, and
probes gateway health best-effort.Examples (install-cli.sh)
- Default
- Custom prefix + version
- Git install
- Automation JSON output
- Run onboarding
Flags reference
Flags reference
Environment variables reference
Environment variables reference
install.ps1
Flow (install.ps1)
1
Ensure PowerShell + Windows environment
Requires PowerShell 5+.
2
Ensure Node.js 24 by default
If missing, attempts install via winget, then Chocolatey, then Scoop. Node 22 LTS, currently
22.14+, remains supported for compatibility.3
Install FluffBuzz
npmmethod (default): global npm install using selected-Taggitmethod: clone/update repo, install/build with pnpm, and install wrapper at%USERPROFILE%\.local\bin\fluffbuzz.cmd
4
Post-install tasks
- Adds needed bin directory to user PATH when possible
- Refreshes a loaded gateway service best-effort (
fluffbuzz gateway install --force, then restart) - Runs
fluffbuzz doctor --non-interactiveon upgrades and git installs (best effort)
Examples (install.ps1)
- Default
- Git install
- GitHub main via npm
- Custom git directory
- Dry run
- Debug trace
Flags reference
Flags reference
Environment variables reference
Environment variables reference
If
-InstallMethod git is used and Git is missing, the script exits and prints the Git for Windows link.CI and automation
Use non-interactive flags/env vars for predictable runs.- install.sh (non-interactive npm)
- install.sh (non-interactive git)
- install-cli.sh (JSON)
- install.ps1 (skip onboarding)
Troubleshooting
Why is Git required?
Why is Git required?
Git is required for
git install method. For npm installs, Git is still checked/installed to avoid spawn git ENOENT failures when dependencies use git URLs.Why does npm hit EACCES on Linux?
Why does npm hit EACCES on Linux?
Some Linux setups point npm global prefix to root-owned paths.
install.sh can switch prefix to ~/.npm-global and append PATH exports to shell rc files (when those files exist).Windows: "npm error spawn git / ENOENT"
Windows: "npm error spawn git / ENOENT"
Install Git for Windows, reopen PowerShell, rerun installer.
Windows: "fluffbuzz is not recognized"
Windows: "fluffbuzz is not recognized"
Run
npm config get prefix and add that directory to your user PATH (no \bin suffix needed on Windows), then reopen PowerShell.Windows: how to get verbose installer output
Windows: how to get verbose installer output
install.ps1 does not currently expose a -Verbose switch.
Use PowerShell tracing for script-level diagnostics:fluffbuzz not found after install
fluffbuzz not found after install
Usually a PATH issue. See Node.js troubleshooting.