Webpacker and JavaScript bundling in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you run bin/webpack in a Rails app using Webpacker?

You run bin/webpack in your Rails project that uses Webpacker. What is the main result of this command?

A It compiles and bundles JavaScript files into a single pack file in <code>public/packs</code>.

B It starts a Rails server to serve JavaScript files dynamically.

C It deletes all JavaScript files from the <code>app/javascript</code> folder.

D It installs new JavaScript packages from <code>package.json</code>.

💡 Hint

Think about what bundling means for JavaScript files in Rails.

Running bin/webpack compiles and bundles JavaScript files into optimized packs that Rails can serve efficiently from public/packs.

📝 Syntax

intermediate

Which Webpacker config file defines the entry points for JavaScript bundling?

In a Rails app using Webpacker, which file specifies the JavaScript entry points that Webpack uses to start bundling?

A config/webpack/environment.js

B app/javascript/packs/application.js

C package.json

D config/webpacker.yml

💡 Hint

Look for the JavaScript file that acts as the entry point for bundling.

The app/javascript/packs/application.js file defines the JavaScript entry points that Webpack uses to start bundling.

🔧 Debug

advanced

Why does this Webpacker build fail with a syntax error?

Given this JavaScript pack file content, why does Webpacker fail to build it?

import React from 'react'
import ReactDOM from 'react-dom'

const App = () => {
  return 
Hello World
}

ReactDOM.render(, document.getElementById('root'))

A The import statements must use double quotes instead of single quotes.

B ReactDOM.render is deprecated and causes a build error.

C The <code>document.getElementById</code> call is invalid in Webpacker.

D The JSX syntax requires a Babel loader configured, which is missing.

💡 Hint

Think about what Webpack needs to understand JSX syntax.

Webpack needs Babel configured with a loader to transform JSX into valid JavaScript. Without it, the build fails with a syntax error.

❓ state_output

advanced

What is the output of this Webpacker manifest JSON after bundling?

After running Webpacker, the manifest.json file contains mappings of source files to compiled assets. Given this snippet:

{
  "application.js": "/packs/js/application-123abc.js",
  "styles.css": "/packs/css/styles-456def.css"
}

What does this mean for the Rails app?

A The manifest file causes Webpacker to delete the original source files.

B Rails will ignore these files and serve the originals from <code>app/javascript</code>.

C Rails will serve the compiled JavaScript and CSS files with hashed names for caching.

D The manifest file is only used for development and ignored in production.

💡 Hint

Think about why hashed filenames are used in web apps.

The manifest maps source files to compiled assets with unique hashes to enable caching and cache busting in browsers.

🧠 Conceptual

expert

Which statement best describes the role of Webpacker in modern Rails apps?

Choose the most accurate description of what Webpacker does in a Rails application.

A Webpacker manages JavaScript and CSS bundling, allowing Rails to use modern JavaScript tools and frameworks seamlessly.

B Webpacker only handles CSS preprocessing and does not affect JavaScript files.

C Webpacker replaces the Rails asset pipeline entirely and removes the need for Sprockets.

D Webpacker is a Rails server extension that dynamically compiles assets on every request.

💡 Hint

Consider what Webpacker adds to Rails compared to the traditional asset pipeline.

Webpacker integrates modern JavaScript bundling tools into Rails, managing JS and CSS assets but does not fully replace Sprockets.