Bundler for dependency resolution in Ruby - Step-by-Step Execution

Concept Flow - Bundler for dependency resolution

Start: Gemfile with dependencies

↓

Run `bundle install` command

↓

Bundler reads Gemfile

↓

Resolve dependencies and versions

↓

Download missing gems

↓

Install gems locally

↓

Create/update Gemfile.lock

↓

Ready to use gems in project

↓

End

Bundler reads your Gemfile, finds the right gem versions, installs them, and locks them in Gemfile.lock for your project.

Execution Sample

Ruby

source 'https://rubygems.org'
gem 'rack', '~> 2.2'
gem 'puma', '~> 5.0'

This Gemfile lists two gems with version rules for Bundler to install.

Execution Table

Step	Action	Details	Result
1	Read Gemfile	Found gems: rack ~> 2.2, puma ~> 5.0	Proceed to resolve dependencies
2	Resolve rack version	Find latest rack matching ~> 2.2	Select rack 2.2.4
3	Resolve puma version	Find latest puma matching ~> 5.0	Select puma 5.6.4
4	Check dependencies of rack	rack has no conflicting dependencies	No conflicts
5	Check dependencies of puma	puma depends on nio4r ~> 2.0	Add nio4r ~> 2.0 to install list
6	Resolve nio4r version	Find latest nio4r matching ~> 2.0	Select nio4r 2.5.8
7	Download gems	rack 2.2.4, puma 5.6.4, nio4r 2.5.8	Gems downloaded
8	Install gems	Install all downloaded gems	Gems installed locally
9	Update Gemfile.lock	Lock versions for rack, puma, nio4r	Gemfile.lock updated
10	Finish	All dependencies resolved and installed	Ready to use gems

💡 All gems resolved and installed, Gemfile.lock created to lock versions

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 6	Final
rack_version	none	2.2.4	2.2.4	2.2.4	2.2.4
puma_version	none	none	5.6.4	5.6.4	5.6.4
nio4r_version	none	none	none	2.5.8	2.5.8
gems_to_install	empty	rack 2.2.4	rack 2.2.4, puma 5.6.4	rack 2.2.4, puma 5.6.4, nio4r 2.5.8	same

Key Moments - 3 Insights

Why does Bundler add nio4r even though it wasn't in the Gemfile?

Bundler checks dependencies of gems listed in Gemfile. Puma depends on nio4r, so Bundler adds it automatically (see execution_table step 5).

What does the '~>' symbol mean in gem versions?

It means 'compatible with'. For example, '~> 2.2' means any version >= 2.2 and < 3.0, so Bundler picks the latest matching version (see execution_table steps 2 and 3).

Why is Gemfile.lock important?

It locks exact gem versions so everyone uses the same ones, avoiding surprises. Bundler updates it after installing gems (see execution_table step 9).

Visual Quiz - 3 Questions

Look at the execution_table, what version of rack does Bundler select?

A 2.3.0

B 2.2.4

C 5.0.0

D Not selected

💡 Hint

Check execution_table row 2 where rack version is resolved.

At which step does Bundler add nio4r to the install list?

A Step 5

B Step 7

C Step 3

D Step 9

💡 Hint

Look at execution_table row 5 where puma's dependencies are checked.

If the Gemfile had no version constraints, how would the execution_table change?

A Bundler would fail to resolve dependencies

B Bundler would pick the oldest versions

C Bundler would pick the latest versions without restrictions

D Bundler would skip installing gems

💡 Hint

Version constraints guide Bundler; no constraints means latest versions (see variable_tracker for version selection).

Concept Snapshot

Bundler reads your Gemfile listing gems and version rules.
It resolves compatible gem versions and dependencies.
Downloads and installs gems locally.
Creates Gemfile.lock to lock versions.
Run with `bundle install` to set up your Ruby project gems.

Full Transcript

Bundler is a tool that helps Ruby projects manage their gem dependencies. When you write a Gemfile listing gems and version rules, Bundler reads it and finds the best matching versions. It also checks each gem's dependencies and adds those automatically. Then Bundler downloads and installs all needed gems locally. Finally, it creates or updates a Gemfile.lock file that locks the exact versions used. This ensures everyone working on the project uses the same gem versions. Running `bundle install` triggers this process. For example, if your Gemfile lists rack and puma with version constraints, Bundler picks the latest versions matching those constraints, finds puma's dependency nio4r, installs all three gems, and locks their versions in Gemfile.lock.