Skip to content

docs: clarify webpack loader execution order (right-to-left) #8136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mr-baraiya wants to merge 2 commits into
base: main
Choose a base branch
from
+10 −5
Open

docs: clarify webpack loader execution order (right-to-left) #8136

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0317ee7
docs: clarify webpack loader execution order (right-to-left)
mr-baraiya Mar 29, 2026
5723f45
docs: clarify webpack loader execution order (right-to-left)
mr-baraiya Mar 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions src/content/guides/asset-management.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ contributors:
- astonizer
- snitin315
- Brennvo
- mr-baraiya
---

If you've been following the guides from the start, you will now have a small project that shows "Hello webpack". Now let's try to incorporate some other assets, like images, to see how they can be handled.
Expand Down Expand Up @@ -95,15 +96,19 @@ npm install --save-dev style-loader css-loader
};
```

Module loaders can be chained. Each loader in the chain applies transformations to the processed resource. A chain is executed in reverse order. The first loader passes its result (resource with applied transformations) to the next one, and so forth. Finally, webpack expects JavaScript to be returned by the last loader in the chain.
Loaders in webpack are executed from **right to left** (i.e., from last to first in the `use` array).

The above order of loaders should be maintained: [`'style-loader'`](/loaders/style-loader) comes first and followed by [`'css-loader'`](/loaders/css-loader). If this convention is not followed, webpack is likely to throw errors.
For example:

T> webpack uses a regular expression to determine which files it should look for and serve to a specific loader. In this case, any file that ends with `.css` will be served to the `style-loader` and the `css-loader`.
```js
use: ["style-loader", "css-loader"];
```

Here, `css-loader` runs first and processes the CSS, followed by `style-loader`, which injects the result into the DOM.

This enables you to `import './style.css'` into the file that depends on that styling. Now, when that module is run, a `<style>` tag with the stringified css will be inserted into the `<head>` of your html file.
So even though `style-loader` appears before `css-loader` in the array, the execution happens in reverse order.

Let's try it out by adding a new `style.css` file to our project and import it in our `index.js`:
If this order is not maintained, webpack may throw errors.

**project**

Expand Down
Loading