Course contentsShow
← Web Development
Lesson 1389 of 2,98225. Build Tools and BundlersFree lesson

Loaders: Processing Non-JavaScript Files

Using loaders to transform CSS, images, and other assets into modules Webpack can bundle.

Loaders: Processing Non-JavaScript Files

You'll learn how Webpack loaders enable you to import and bundle non-JavaScript assets like CSS, images, and fonts as if they were JavaScript modules.

The Core Idea

By default, Webpack only understands JavaScript and JSON files. But modern web applications need CSS stylesheets, images, fonts, and other assets. Loaders are Webpack's way of teaching it to handle these different file types by transforming them into modules that can be included in your dependency graph and bundled alongside your JavaScript.

Think of loaders as translators: when Webpack encounters a file it doesn't understand, a loader steps in to convert that file into something Webpack can work with.

How Loaders Work

When you import a CSS file or image in your JavaScript:

import './styles.css';
import logo from './logo.png';

Webpack uses configured loaders to process these files. Each loader performs a specific transformation:

  • css-loader interprets @import and url() in CSS files
  • style-loader injects CSS into the DOM
  • file-loader emits files to the output directory and returns their URLs
  • url-loader can inline small files as data URLs

Loaders are configured in webpack.config.js using the module.rules array. Each rule specifies which files to match (using regex patterns) and which loader(s) to apply. Loaders process files from right to left (or bottom to top), allowing you to chain multiple transformations.

This approach lets you treat all assets as dependencies, ensuring Webpack knows exactly what your application needs and can optimize accordingly.

Key Takeaway: Loaders transform non-JavaScript files into modules Webpack can bundle, turning imports of CSS, images, and other assets into first-class citizens in your dependency graph.