Bundler for dependency resolution in Ruby - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to install Bundler using RubyGems.

Ruby

gem install [1]

Drag options to blanks, or click blank then click option'

Arails

Bbundler

Crake

Dsinatra

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to install 'rails' instead of 'bundler'.

Using 'bundle' instead of 'bundler' in the install command.

You use gem install bundler to install Bundler, the Ruby dependency manager.

2fill in blank

medium

Complete the command to create a Gemfile with Bundler.

Ruby

bundle [1]

Drag options to blanks, or click blank then click option'

Aupdate

Binstall

Cexec

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bundle install' to create a Gemfile (it installs gems instead).

Using 'bundle update' which updates gems but does not create a Gemfile.

The bundle init command creates a new Gemfile in your project.

3fill in blank

hard

Fix the error in the Gemfile to specify the version of the 'rails' gem.

Ruby

gem 'rails', '[1]'

Drag options to blanks, or click blank then click option'

A>= 6.0.0

B6.0.0

C~> 6.0

Dlatest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latest' which is not a valid version string.

Using exact version '6.0.0' which is too strict for updates.

The ~> 6.0 syntax means compatible with version 6.0, which is the correct way to specify version constraints in Bundler.

4fill in blank

hard

Fill both blanks to install gems and update the Gemfile.lock file.

Ruby

bundle [1] && bundle [2]

Drag options to blanks, or click blank then click option'

Ainstall

Bupdate

Cexec

Dclean

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'exec' which runs a command but does not install or update gems.

Using 'clean' which removes unused gems but does not install or update.

bundle install installs the gems listed in the Gemfile, and bundle update updates the gems and the Gemfile.lock file.

5fill in blank

hard

Fill all three blanks to define a gem with a version constraint and group it under development.

Ruby

group :development do
  gem '[1]', '[2]'
end

bundle [3]

Drag options to blanks, or click blank then click option'

Apry

B~> 0.13.1

Cinstall

Drspec

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'rspec' gem but forgetting to specify version.

Using 'bundle update' instead of 'bundle install' after editing Gemfile.

This code adds the 'pry' gem with version '~> 0.13.1' to the development group, then runs bundle install to install it.

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