BUNDLE-CHECK(1)

πŸ“¦ version 4.0.6, in centos-stream 10

πŸ’– BUNDLE-CHECK(1) πŸ’–

okay bestie, welcome to the bundle-check page β€” it lives in the General Commands Manual and it is literally the vibe check for your gems 🫢


✨ NAME ✨

bundle-check β€” verifies if dependencies are satisfied by installed gems πŸ¦‹


✨ SYNOPSIS ✨

bundle check [--dry-run] [--gemfile=FILE]

✨ DESCRIPTION ✨

so basically check goes snooping around your local machine, looking for every single gem that your Gemfile is asking for. πŸ”

if it finds all of them? slay. Bundler prints a success message and exits with a status of 0. main character energy, no notes. πŸ‘‘

if not? πŸ’€ the first missing gem gets called out by name, and Bundler exits with status 1. not mean, just honest.

and if the lockfile needs to be updated, then it will be resolved using the gems installed on the local machine β€” but only if they satisfy the requirements. no cap. ✨


✨ OPTIONS ✨


🌸 that's the whole page, bestie 🌸

this little icon was brought to you by April 2026, and the manual it came from is BUNDLE-CHECK(1). go check your gems, you got this πŸ’…πŸ’–

πŸ“¦ where this page comes from
  • centos-stream 10: ruby4.0 4.0.6-37.el10 Β· (Ruby OR BSD-2-Clause) AND (Ruby OR BSD-2-Clause OR GPL-1.0-or-later) AND BSD-3-Clause AND (GPL-3.0-or-later WITH Bison-exception-2.2) AND ISC AND LicenseRef-Fedora-Public-Domain AND MIT AND CC0-1.0 AND zlib AND Unicode-DFS-2015 AND HPND-Markus-Kuhn AND Ruby-pty AND (Ruby OR BSD-2-Clause OR Python-2.0.1) AND BSD-2-Clause AND (Apache-2.0 OR BSL-1.0) AND GPL-2.0-only AND CC-BY-2.5 AND OFL-1.1-RFN AND BSL-1.0
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms