BUNDLE-CHECK(1)
π 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 β¨
--dry-runβ locks the[Gemfile(5)][Gemfile(5)]before running the command. π--gemfile=GEMFILEβ use the specified gemfile instead of the[Gemfile(5)][Gemfile(5)]. π
πΈ 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 9: rubygem-bundler 4.0.16-35.module_el9+1443+8853c6a2 Β· MIT AND (Ruby OR BSD-2-Clause)
- fedora 44: rubygem-bundler 4.0.20-39.fc44
- fedora 44: rubygem-bundler 4.0.20-40.fc44 Β· MIT AND (Ruby OR BSD-2-Clause)
- ubuntu stonking: ruby-bundler 4.0.18-1 Β· MIT OR Custom
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms