diff --git a/src/content/guides/asset-management.mdx b/src/content/guides/asset-management.mdx index 45ce536199ba..7b71b2d59215 100644 --- a/src/content/guides/asset-management.mdx +++ b/src/content/guides/asset-management.mdx @@ -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. @@ -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 `