Why gem management matters in Ruby - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output when requiring gems without version control?

Consider a Ruby project that requires the 'json' gem. If the system has multiple versions of 'json' installed, what will be the output of the following code when run without specifying a gem version?

Ruby

require 'json'
puts JSON.generate({hello: 'world'})

A {"hello":"world"}

B LoadError: cannot load such file -- json

C TypeError: no implicit conversion of Symbol into String

D SyntaxError: unexpected token

💡 Hint

Think about what happens when Ruby loads the default gem version.

Without specifying a gem version, Ruby loads the default installed version of the gem. The code outputs the JSON string representation of the hash.

🧠 Conceptual

intermediate

Why lock gem versions in a Gemfile?

Why is it important to lock gem versions in a Gemfile when managing Ruby projects?

A To reduce the size of the project by removing unused gems.

B To allow gems to update automatically to the latest versions without restrictions.

C To ensure consistent gem versions across different environments and avoid unexpected bugs.

D To speed up the Ruby interpreter during runtime.

💡 Hint

Think about what happens if different developers use different gem versions.

Locking gem versions ensures everyone uses the same gem versions, preventing bugs caused by version differences.

🔧 Debug

advanced

Identify the error caused by missing gem version specification

Given the following Gemfile and Ruby code, what error will occur when running the code if the gem version is not specified and multiple versions are installed? Gemfile: gem 'nokogiri' Ruby code: require 'nokogiri' puts Nokogiri::HTML('

Hello

').text

Ruby

require 'nokogiri'
puts Nokogiri::HTML('<h1>Hello</h1>').text

A LoadError: cannot load such file -- nokogiri

B NoMethodError: undefined method 'HTML' for Nokogiri:Module

C ArgumentError: wrong number of arguments

D Outputs 'Hello' without error

💡 Hint

Consider what happens if the gem loads correctly.

If nokogiri is installed, even without version locking, the code outputs 'Hello' as expected.

📝 Syntax

advanced

Which Gemfile syntax correctly specifies a gem version?

Select the correct syntax to specify version 2.1.0 of the 'rails' gem in a Gemfile.

A gem 'rails', '2.1.0'

B gem rails, version: '2.1.0'

C gem 'rails' version '2.1.0'

D gem 'rails' => '2.1.0'

💡 Hint

Look for the correct Ruby method argument syntax.

The correct syntax uses a comma to separate the gem name and version string.

🚀 Application

expert

How does Bundler ensure consistent gem versions across environments?

Bundler uses a special file to lock gem versions. What is the name of this file and how does Bundler use it to maintain consistency?

A Gemfile.lock; Bundler ignores this file and installs latest gem versions always.

B Gemfile.lock; Bundler reads this file to install exact gem versions specified during bundle install.

C Gemfile; Bundler uses this file to lock gem versions and ignores Gemfile.lock.

D bundle.lock; Bundler uses this file to cache gem downloads but not versions.

💡 Hint

Think about the file Bundler creates after installing gems.

Bundler creates Gemfile.lock to record exact gem versions and uses it to install the same versions on other machines.