BUNDLE-INIT(1)

💖 BUNDLE-INIT(1) 💖

okay so real quick — this is a page from the General Commands Manual, and it's all about bundle init, the little command that hands you a fresh Gemfile like it's passing you a boba 🧋. Bestie, it's genuinely so simple you're gonna slay this.

---

✨ NAME ✨

bundle-init — literally just generates a Gemfile into the current working directory 💅

---

🦋 SYNOPSIS 🦋

bundle init [--gemspec=FILE]

---

🌸 DESCRIPTION 🌸

So init generates a default [Gemfile(5)][Gemfile(5)] right in your current working directory. That's it. That's the whole vibe. 🎀

But here's the cute part — when you're adding a [Gemfile(5)][Gemfile(5)] to a gem that already has a gemspec, the --gemspec option will automatically add each dependency listed in the gemspec file straight into the newly created [Gemfile(5)][Gemfile(5)]. No cap, it just does it for you. 🔥

---

💅 OPTIONS 💅

• --gemspec=GEMSPEC — use the .gemspec you specify to create the [Gemfile(5)][Gemfile(5)]. iconic behavior honestly ✨
• --gemfile=GEMFILE — use the name you specify for the gemfile instead of Gemfile. yeah you can rename it, main character energy 👑

---

🎀 FILES 🎀

Included in the default [Gemfile(5)][Gemfile(5)] that gets generated is this line:

# frozen_string_literal: true

That's a magic comment, and it was supported for the first time in Ruby 2.3. 🪄 The presence of this line results in all string literals in the file being implicitly frozen. lowkey a big deal, fr fr 🧊

---

🌈 SEE ALSO 🌈

Gemfile(5) — https://bundler.io/man/gemfile.5.html

---

okay that's the whole page bestie, go forth and init 🌟

mwah 💋 — this was the General Commands Manual entry for BUNDLE-INIT(1), dated April 2026.