BUNDLE(1)

🎀 NAME 🎀

okay so bestie, meet bundle — the BUNDLE(1) page from the General Commands Manual — and it's literally all about Ruby Dependency Management 💖. no cap, this is the main character of your Ruby app's dependency saga.

✨ SYNOPSIS ✨

bundle COMMAND [--no-color] [--verbose] [ARGS]

💖 DESCRIPTION 💖

Bundler is the bestie who manages an application's dependencies through their entire life, across many machines, systematically and repeatably. periodt. it's giving "your gems are handled, bestie" 🫶.

If you're just getting started, the bundler website at https://bundler.io has the getting-started info ☕, and Gemfile(5) has the full tea on the Gemfile format ✨.

🧚 OPTIONS 🧚

• --no-color — prints all output without color. if you're not in a colorful mood, this is your girl 🎀.
• --retry, -r — specifies the number of times you wish to attempt network commands. lowkey useful when the network is being dramatic 🌐.
• --verbose, -V — prints out additional logging information. for when you want the whole group-chat transcript, iykyk 🔍.

👑 BUNDLE COMMANDS 👑

Bundler divides the bundle subcommands into two little cliques: primary commands and utilities 💅. here's the whole lineup so you never get left on read.

🔥 PRIMARY COMMANDS 🔥

• bundle install(1) · bundle-install.1.html — installs the gems specified by the Gemfile or Gemfile.lock. the classic "make it work" moment ✨.
• bundle update(1) · bundle-update.1.html — updates dependencies to their latest versions. it's giving fresh gems, no cap 🔥.
• bundle cache(1) · bundle-cache.1.html — packages the .gem files required by your application into the vendor/cache directory. aliases: bundle package, bundle pack 🎀.
• bundle exec(1) · bundle-exec.1.html — executes a script in the current bundle. main character energy for your scripts 💅.
• bundle config(1) · bundle-config.1.html — specifies and reads configuration options for Bundler. the settings bestie ⚙️.
• bundle help(1) · bundle-help.1.html — displays detailed help for each subcommand. when you need the lore 🧚.

🌈 UTILITIES 🌈

• bundle add(1) · bundle-add.1.html — adds the named gem to the Gemfile and runs bundle install. one-step gem adoption, slay 🍓.
• bundle binstubs(1) · bundle-binstubs.1.html — generates binstubs for executables in a gem. cute little executable shortcuts ✨.
• bundle check(1) · bundle-check.1.html — determines whether the requirements for your application are installed and available to Bundler. the vibe check for your deps ✅.
• bundle show(1) · bundle-show.1.html — shows the source location of a particular gem in the bundle. where is that gem living? found her 🔍.
• bundle outdated(1) · bundle-outdated.1.html — shows all of the outdated gems in the current bundle. not me checking who needs a glow-up 👀.
• bundle console(1) (deprecated) — starts an IRB session in the current bundle. deprecated, bestie, so treat it like an old post you don't repost 🫠.
• bundle open(1) · bundle-open.1.html — opens an installed gem in the editor. editor era 💻.
• bundle lock(1) · bundle-lock.1.html — generates a lockfile for your dependencies. locking it in, literally 🔒.
• bundle init(1) · bundle-init.1.html — generates a simple Gemfile, placed in the current directory. starter-pack energy 🎁.
• bundle gem(1) · bundle-gem.1.html — creates a simple gem, suitable for development with Bundler. new gem, who dis 💎.
• bundle platform(1) · bundle-platform.1.html — displays platform compatibility information. compatibility check, iykyk 🧚.
• bundle clean(1) · bundle-clean.1.html — cleans up unused gems in your Bundler directory. declutter szn 🧹.
• bundle doctor(1) · bundle-doctor.1.html — displays warnings about common problems. the friend who tells you to drink water and check your deps 🩺.
• bundle remove(1) · bundle-remove.1.html — removes gems from the Gemfile. breaking up with a gem, gently 💔.
• bundle plugin(1) · bundle-plugin.1.html — manages Bundler plugins. plugin management, periodt 🔌.
• bundle version(1) · bundle-version.1.html — prints Bundler version information. the "what version are we on" check 💬.

🦋 PLUGINS 🦋

if you run a command that isn't listed in PRIMARY COMMANDS or UTILITIES, Bundler will try to find an executable on your path named bundler-<command> and execute it, passing down any extra arguments to it. so yes, your custom command can absolutely have main character energy 🌟.

---

mwah 💋 that's the whole BUNDLE(1) page from the General Commands Manual — served fresh with April 2026 energy, and your girl BUNDLE(1) is signing off. go manage those dependencies, bestie 🫶✨