Bundler for dependency resolution in Ruby - Mini Project: Build & Apply

Bundler for Dependency Resolution

📖 Scenario: You are building a simple Ruby project that needs external libraries (gems) to work. To manage these libraries easily, you will use Bundler, a tool that helps Ruby projects keep track of and install the right versions of gems.

🎯 Goal: Create a Ruby project that uses Bundler to manage dependencies. You will write a Gemfile listing the gems your project needs, configure Bundler, install the gems, and then write Ruby code that uses one of the installed gems.

📋 What You'll Learn

Create a Gemfile with specific gems and versions

Use Bundler to install the gems

Write Ruby code that requires and uses a gem from the Gemfile

Print output showing the gem is working

💡 Why This Matters

🌍 Real World

Bundler is used in almost every Ruby project to manage external libraries safely and easily. It helps avoid version conflicts and makes sharing projects simple.

💼 Career

Knowing how to use Bundler is essential for Ruby developers, especially when working on web apps, scripts, or any project that depends on third-party gems.

1

Create a Gemfile with dependencies

Create a file named Gemfile and write these exact lines inside it:
source 'https://rubygems.org'
gem 'colorize', '~> 0.8.1'

Ruby

# Create a Gemfile with the source and gem 'colorize' version '~> 0.8.1'
# Your code here

Hint

The Gemfile tells Bundler which gems to install. Use the exact gem name and version.

2

Install gems using Bundler

Run the command bundle install in your terminal to install the gems listed in the Gemfile. Then create a Ruby file named app.rb and write require 'bundler/setup' at the top.

Ruby

source 'https://rubygems.org'
gem 'colorize', '~> 0.8.1'

# In app.rb, write require 'bundler/setup'
# Your code here

Hint

Running bundle install downloads the gems. The require 'bundler/setup' line loads Bundler in your Ruby script.

3

Require and use the gem in Ruby code

In app.rb, add require 'colorize' below require 'bundler/setup'. Then write puts 'Hello, Bundler!'.colorize(:green) to print green text.

Ruby

source 'https://rubygems.org'
gem 'colorize', '~> 0.8.1'

# app.rb
require 'bundler/setup'
# Add require 'colorize' and print green text
# Your code here

Hint

The colorize gem lets you print colored text. Use puts with .colorize(:green) to show green text.

4

Run the Ruby script and see the output

Run ruby app.rb in your terminal. The output should be the text Hello, Bundler! shown in green color.

Ruby

source 'https://rubygems.org'
gem 'colorize', '~> 0.8.1'

# app.rb
require 'bundler/setup'
require 'colorize'
puts 'Hello, Bundler!'.colorize(:green)

# Run the script and observe the output
# Your code here

Hint

When you run the script, the text should appear in green if your terminal supports colors.

Practice

1. What is the main purpose of Bundler in a Ruby project?

easy

A. To run Ruby code faster by caching results

B. To compile Ruby code into machine language

C. To create user interfaces for Ruby applications

D. To manage and install gem dependencies with specific versions

Solution

1. Step 1: Understand Bundler's role

   Bundler is designed to handle gem dependencies and ensure the correct versions are used in a project.

2. Step 2: Compare options

   Options B, C, and D describe unrelated tasks like compiling, UI creation, or caching, which Bundler does not do.

3. Final Answer:

   To manage and install gem dependencies with specific versions -> Option D

4. Quick Check:

   Bundler = dependency manager [OK]

Hint: Bundler manages gems and versions for your Ruby project [OK]

Common Mistakes:

• Confusing Bundler with Ruby interpreter
• Thinking Bundler compiles code
• Assuming Bundler creates user interfaces

2. Which of the following is the correct command to install gems listed in a Gemfile using Bundler?

easy

A. bundle install

B. gem install

C. bundle update

D. ruby install

Solution

1. Step 1: Identify the command to install gems from Gemfile

   The command bundle install reads the Gemfile and installs the specified gems.

2. Step 2: Differentiate from other commands

   gem install installs a single gem, bundle update updates gems, and ruby install is invalid.

3. Final Answer:

   bundle install -> Option A

4. Quick Check:

   Install gems with bundle install [OK]

Hint: Use 'bundle install' to install all gems from Gemfile [OK]

Common Mistakes:

• Using 'gem install' instead of 'bundle install'
• Confusing 'bundle update' with install
• Typing invalid commands like 'ruby install'

3. Given this Gemfile content:

source 'https://rubygems.org'
gem 'rack', '~> 2.2.0'
gem 'puma', '5.0.4'

What will Bundler do when you run bundle install?

medium

A. Install rack version 2.2.x and puma version 5.0.4

B. Install latest versions of rack and puma ignoring specified versions

C. Install rack version 2.2.0 exactly and puma version 5.0.4

D. Fail because version constraints are invalid

Solution

1. Step 1: Understand version constraints in Gemfile

   The '~> 2.2.0' means any version >= 2.2.0 and < 2.3.0 for rack. The puma gem is fixed at 5.0.4.

2. Step 2: What does Bundler do on install?

   Bundler installs rack in the 2.2.x range and puma exactly at 5.0.4, respecting constraints.

3. Final Answer:

   Install rack version 2.2.x and puma version 5.0.4 -> Option A

4. Quick Check:

   ~> means compatible version range [OK]

Hint: ~> means 'compatible with' version, not exact [OK]

Common Mistakes:

• Thinking '~>' means exact version
• Assuming latest versions install ignoring constraints
• Believing version constraints cause install failure

4. You run bundle install but get an error: Could not find gem 'rails (~> 6.1.0)' in any of the sources. What is the most likely cause?

medium

A. The Gemfile is missing the source URL

B. The specified version of rails is not available in the gem sources

C. You forgot to run bundle update before install

D. The Ruby version is incompatible with rails

Solution

1. Step 1: Analyze the error message

   The error says Bundler cannot find the gem 'rails' with version '~> 6.1.0' in any source.

2. Step 2: Identify common causes

   This usually means the gem version is not published or available in the specified gem sources.

3. Final Answer:

   The specified version of rails is not available in the gem sources -> Option B

4. Quick Check:

   Missing gem version causes install error [OK]

Hint: Check gem version availability if install fails [OK]

Common Mistakes:

• Assuming missing source URL causes this error
• Thinking 'bundle update' fixes missing gem versions
• Blaming Ruby version without checking gem availability

5. You want to ensure your Ruby project always uses the exact same gem versions on any machine. Which Bundler feature should you use?

hard

A. bundle update to refresh gems

B. gem uninstall to remove old gems

C. Gemfile.lock to lock gem versions

D. bundle exec to run commands

Solution

1. Step 1: Understand version consistency needs

   To keep gem versions consistent across machines, Bundler uses a lock file that records exact versions installed.

2. Step 2: Identify the correct Bundler feature

   The Gemfile.lock file stores the exact gem versions after running bundle install.

3. Step 3: Differentiate other options

   bundle update refreshes gems, gem uninstall removes gems, and bundle exec runs commands in context but doesn't lock versions.

4. Final Answer:

   Gemfile.lock to lock gem versions -> Option C

5. Quick Check:

   Gemfile.lock locks versions for consistency [OK]

Hint: Use Gemfile.lock to freeze gem versions across machines [OK]

Common Mistakes:

• Confusing bundle update with locking versions
• Thinking bundle exec locks gem versions
• Ignoring Gemfile.lock file importance