BUNDLE-OPEN(1)

✨ NAME ✨

bundle-open — the lil' bestie that pops open the source directory for a gem in your bundle 🫶

---

🌸 SYNOPSIS 🌸

bundle open [GEM] [--path=PATH]

---

💅 DESCRIPTION 💅

Okay so picture this: you've got a gem sitting all cozy in your bundle, and you wanna peek at its actual source code. That's literally what bundle open is for — it opens up the source directory of the GEM you hand it, right there in your editor. Main character behaviour, honestly. 👑

But — and this is the part people always forget — for any of this to work, your EDITOR or BUNDLER_EDITOR environment variable has to be set. No editor variable, no vibes. It's giving "I forgot my keys." 🔑

Let's do examples, because examples ate and left no crumbs:

bundle open 'rack'

This one opens the source directory for the 'rack' gem in your bundle. Boom. Straight to the source. 🌈

bundle open 'rack' --path 'README.md'

And this one? This one opens the README.md file of the 'rack' gem source in your bundle. So like, you can point it at a specific file instead of the whole directory. Iconic. ⭐

---

🎀 OPTIONS 🎀

• --path[=PATH] — specify the GEM source relative path you wanna open. That's it, that's the whole option. 💖

---

Quick vibe check: if EDITOR and BUNDLER_EDITOR are both unset, this whole thing is not gonna slay. Set one first. 🌸

---

Okay bestie that's the whole page — bundle-open(1) from the General Commands Manual, dated April 2026. Go open some source code, you absolute legend. 💜✨