Skip to Content
DocsCommandsnb bundle

nb bundle

nb bundle [OPTIONS] nb bundle <COMMAND>

With no subcommand, nb bundle installs from the Brewfile (nb bundle install).

Subcommands

SubcommandMeaning
install (alias upgrade)Install and upgrade everything in a Brewfile
checkCheck that everything in a Brewfile is installed and up to date
listList the dependencies in a Brewfile (formulae unless told otherwise)
addAdd entries to a Brewfile (formulae unless told otherwise)
removeRemove entries matching the names from a Brewfile
execRun a command in the build environment for the Brewfile’s formulae
shStart a shell in the build environment for the Brewfile’s formulae
envPrint the build environment for the Brewfile’s formulae as exports
cleanupUninstall what a Brewfile does not list
dumpWrite what is installed into a Brewfile

Options

FlagMeaning
--file <FILE>Read this Brewfile (- for standard input) instead of ./Brewfile or $HOMEBREW_BUNDLE_FILE
--globalRead ~/.Brewfile (or $HOMEBREW_BUNDLE_FILE_GLOBAL)
--no-upgradeDo not upgrade outdated dependencies
--upgradeUpgrade outdated dependencies even if $HOMEBREW_BUNDLE_NO_UPGRADE is set
--upgrade-formulae <FORMULAE>Upgrade these comma-separated formulae even with --no-upgrade (alias --upgrade-formula)
--auto-initInitialize without prompting
-v, --verboseIncrease output verbosity
--quietPrint only failures and the summary

Each subcommand has further options of its own; run nb bundle <COMMAND> --help.

Examples

nb bundle nb bundle --file ~/dotfiles/Brewfile check nb bundle dump

Differences from brew

Bundle is Partial and not yet verified on real macOS hardware. The code also handles vscode, go, cargo, uv, krew, npm and mas entries. flatpak and winget entries, and build args, are reported as failures with the reason, never skipped silently. See Compatibility.

Last updated on