CSS bundling options in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does CSS bundling improve Rails app performance?

In a Rails app using CSS bundling, what is the main benefit of combining multiple CSS files into one bundle?

A It disables CSS caching to ensure styles update instantly on every request.

B It automatically converts CSS to JavaScript for better browser compatibility.

C It reduces the number of HTTP requests, speeding up page load times.

D It splits CSS files into smaller chunks to load only needed styles per page.

💡 Hint

Think about how browsers load files and how fewer files can mean faster loading.

Bundling CSS combines many files into one, so the browser makes fewer requests. This reduces waiting time and speeds up page loading.

❓ component_behavior

intermediate

What happens when you enable CSS bundling in Rails?

Given a Rails app with multiple CSS files, what is the expected behavior after enabling CSS bundling?

A All CSS files are merged into a single file served to the browser.

B Each CSS file is loaded separately with unique URLs to avoid caching.

C CSS files are converted to inline styles inside HTML files.

D CSS files are ignored and styles are loaded from external CDN only.

💡 Hint

Consider what bundling means for file delivery.

Enabling CSS bundling merges all CSS files into one, reducing requests and simplifying style delivery.

📝 Syntax

advanced

Identify the correct CSS bundling config in Rails

Which of the following is the correct way to configure CSS bundling in config/assets.rb for Rails?

A css_bundling.install('tailwind')

B cssbundling.install :tailwind

C CSSBundling.install :tailwind

D cssBundling.install :tailwind

💡 Hint

Look for the correct method name and symbol usage in Ruby.

The correct syntax uses lowercase method cssbundling.install with a symbol argument :tailwind.

🔧 Debug

advanced

Why does CSS bundling fail to update styles after changes?

After enabling CSS bundling in Rails, you update your CSS but the browser still shows old styles. What is the most likely cause?

A The CSS bundling gem is incompatible with Rails 7.

B Rails does not support CSS bundling with Tailwind CSS.

C The CSS files are not saved in the <code>app/assets/stylesheets</code> folder.

D The CSS bundle is cached by the browser and needs cache clearing or fingerprinting.

💡 Hint

Think about how browsers handle static files and caching.

Browsers cache bundled CSS files. Without cache busting (fingerprinting), updates may not show until cache is cleared.

❓ lifecycle

expert

When is CSS bundling applied during Rails asset pipeline lifecycle?

At what stage in the Rails asset pipeline does CSS bundling typically occur?

A During asset precompilation before deployment to production.

B At runtime when the browser requests CSS files.

C When the Rails server starts, before serving any requests.

D After the browser downloads CSS, during rendering.

💡 Hint

Consider when assets are prepared for production use.

CSS bundling happens during asset precompilation, combining and optimizing CSS before deployment.

Practice

1. What is the main purpose of CSS bundling in a Rails application?

easy

A. To disable CSS caching in browsers

B. To separate CSS files for easier debugging

C. To convert CSS into JavaScript files

D. To combine multiple CSS files into one for faster page loading

Solution

1. Step 1: Understand CSS bundling concept

   CSS bundling means merging many CSS files into a single file to reduce the number of requests a browser makes.

2. Step 2: Identify the benefit in Rails context

   Combining CSS files speeds up page loading by reducing HTTP requests, which is the main goal of bundling.

3. Final Answer:

   To combine multiple CSS files into one for faster page loading -> Option D

4. Quick Check:

   CSS bundling = faster loading [OK]

Hint: Bundling means merging files to speed up loading [OK]

Common Mistakes:

• Thinking bundling separates files instead of combining
• Confusing CSS bundling with JavaScript bundling
• Assuming bundling disables caching

2. Which command correctly installs Tailwind CSS bundling in a Rails project?

easy

A. rails css:install:tailwind

B. rails css:setup:tailwind

C. rails css:bundle:tailwind

D. rails css:compile:tailwind

Solution

1. Step 1: Recall Rails CSS bundling command pattern

   The correct command pattern is rails css:install:<bundler> to install a CSS bundler.

2. Step 2: Match the bundler name

   For Tailwind CSS, the bundler name is 'tailwind', so the command is rails css:install:tailwind.

3. Final Answer:

   rails css:install:tailwind -> Option A

4. Quick Check:

   Install command = rails css:install:tailwind [OK]

Hint: Use rails css:install:<bundler> for setup [OK]

Common Mistakes:

• Using 'setup' or 'bundle' instead of 'install'
• Typing 'compile' which is not a valid command
• Misspelling 'tailwind'

3. Given the command rails css:install:bootstrap, what is the expected outcome?

medium

A. Rails generates JavaScript files for Bootstrap

B. Bootstrap CSS bundling setup files are added to the project

C. The project removes all CSS files

D. The command throws an error because Bootstrap is unsupported

Solution

1. Step 1: Understand the command purpose

   The command rails css:install:bootstrap installs Bootstrap CSS bundling support in the Rails app.

2. Step 2: Identify the expected effect

   This adds necessary Bootstrap CSS files and configuration to enable bundling, not removing files or generating JS.

3. Final Answer:

   Bootstrap CSS bundling setup files are added to the project -> Option B

4. Quick Check:

   rails css:install:bootstrap adds Bootstrap CSS [OK]

Hint: Install commands add setup files, not remove them [OK]

Common Mistakes:

• Thinking it deletes CSS files
• Expecting JavaScript files instead of CSS
• Assuming Bootstrap bundling is unsupported

4. You run rails css:install:sass but get an error. What is the likely cause?

medium

A. You need to install Node.js first

B. You must run the command with sudo

C. The bundler name should be 'dart-sass', not 'sass'

D. Rails does not support any Sass bundler

Solution

1. Step 1: Check the correct bundler name for Sass

   Rails uses 'dart-sass' as the bundler name, not just 'sass'. Using 'sass' causes an error.

2. Step 2: Verify other options

   Running with sudo is unnecessary, Rails supports Sass via dart-sass, and Node.js is not required for this command.

3. Final Answer:

   The bundler name should be 'dart-sass', not 'sass' -> Option C

4. Quick Check:

   Correct bundler name = dart-sass [OK]

Hint: Use exact bundler names like 'dart-sass' [OK]

Common Mistakes:

• Using partial or incorrect bundler names
• Assuming sudo fixes all errors
• Believing Node.js is required for CSS bundling commands

5. You want to switch from Tailwind to Bootstrap CSS bundling in your Rails app. Which steps should you follow?

hard

A. Remove Tailwind files, run rails css:install:bootstrap, then update your CSS imports

B. Run rails css:install:bootstrap directly without removing Tailwind files

C. Delete all CSS files manually and restart the server

D. Change the bundler name in config files without reinstalling

Solution

1. Step 1: Remove existing Tailwind CSS files

   To avoid conflicts, remove Tailwind CSS files and configurations first.

2. Step 2: Install Bootstrap bundling

   Run rails css:install:bootstrap to add Bootstrap bundling setup.

3. Step 3: Update CSS imports

   Modify your CSS files or imports to use Bootstrap styles instead of Tailwind.

4. Final Answer:

   Remove Tailwind files, run rails css:install:bootstrap, then update your CSS imports -> Option A

5. Quick Check:

   Switch bundlers = remove old + install new + update imports [OK]

Hint: Remove old bundler before installing new one [OK]

Common Mistakes:

• Installing new bundler without removing old files
• Only deleting CSS files without reinstalling bundler
• Changing config without running install commands