Brewfiles are text files that list packages to install, similar to package.json for Node.js or requirements.txt for Python. zerobrew provides commands to install packages from Brewfiles and export your installed packages to a Brewfile.
Installing from a Brewfile
Default Brewfile
To install all packages listed in a Brewfile in the current directory:
Or explicitly:
This reads the Brewfile and installs each package sequentially:
==> Installing 5 formulas from Brewfile...
==> Installing jq...
==> Installing wget...
==> Finished installing manifest in 12.34s
Custom file location
To install from a different file:
zb bundle install -f packages.txt
zb bundle install --file ~/my-setup/Brewfile
Install without linking
To install packages without creating symlinks in the prefix:
zb bundle install --no-link
brew directives with quotes:
brew "jq"
brew "wget"
brew "git"
brew "sqlite"
#:
# Development tools
brew "jq" # JSON processor
brew "wget" # File downloader
# Version control
brew "git"
# Can mix and match
brew "jq"
wget
git # inline comments work everywhere
brew "sqlite"
Tap and Cask directives
tap "homebrew/core" # Ignored by zerobrew
brew "jq"
cask "docker" # Prefixed as cask:docker
tap directives are ignored since zerobrew always uses homebrew-core. Cask entries are supported but functionality may be limited compared to CLI formulas.
Exporting to a Brewfile
Default export
To export all installed packages to a Brewfile in the current directory:
Output:
==> Dumped 15 packages to Brewfile
brew directive format:
brew "git"
brew "jq"
brew "sqlite"
brew "wget"
Custom output file
To dump to a different file:
zb bundle dump -f my-packages.txt
zb bundle dump --file ~/backups/Brewfile.2026-02-28
Overwrite existing files
By default, dump will fail if the target file exists:
Error: file Brewfile already exists (use --force to overwrite)
zb bundle dump --force
zb bundle dump -f output.txt --force
Common Workflows
Create a portable development environment
Export your current setup:zb bundle dump -f ~/dotfiles/Brewfile
cd ~/dotfiles
git add Brewfile
git commit -m "Add package manifest"
Restore on a new machine
Clone your dotfiles:git clone https://github.com/user/dotfiles.git
cd dotfiles
Team development environment
Create a shared Brewfile for your project:
# Project dependencies
brew "jq" # JSON parsing in scripts
brew "sqlite" # Local database
brew "git"
# Development tools
brew "ripgrep" # Fast code search
brew "fzf" # Fuzzy finder
Update and sync
After installing new packages, update your Brewfile:
zb install ripgrep fzf
zb bundle dump --force # Update Brewfile
git add Brewfile
git commit -m "Add ripgrep and fzf"
Brewfile Parsing Details
Duplicate handling
Duplicate entries are automatically deduplicated:
brew "jq"
brew "wget"
brew "jq" # This duplicate is ignored
jq and wget are installed (jq appears once).
Empty lines and whitespace
Empty lines and leading/trailing whitespace are ignored:
This is parsed as: jq, wget, git.
Error handling
If the Brewfile contains only comments or is empty:
Error: manifest Brewfile did not contain any formulas
Error: failed to read manifest Brewfile: No such file or directory
Command Reference
zb bundle install
zb bundle install [OPTIONS]
-f, --file <FILE> - Path to Brewfile (default: Brewfile)--no-link - Install without creating symlinks
zb bundle dump
Options:
-f, --file <FILE> - Output file path (default: Brewfile)--force - Overwrite existing file
zb install <formula> - Install individual packageszb list - View all installed packages- Migration Guide - Migrate from Homebrew and export to Brewfile