Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

When do I use 'use' and 'loader' in Webpack 2 module.rules?

I am upgrading my current project to Webpack2, which it was using Webpack1 prior. I have looked into a couple tutorials about upgrading and in general, I do understand.

The issue I keep running into, though, is I'm not sure when to use 'use' and 'loader' in when specifying the module rules (loaders). At first, I thought use replaced loader. I understand this type of syntax:

module: {   rules: [{     test: /\.scss$/,     use: [       {         loader: 'postcss-loader',         options: {           plugins: ...         }       },       'sass-loader'     ]   }] } 

However, when I use the ExtractTextPlugin it doesn't seem to like when it's consdiered a use. I've tried this:

      {         test: /\.scss$/,         use: [           {             loader: ExtractTextPlugin.extract({               fallbackLoader: 'style-loader',               loader: scssLoaders             })           }]       }, 

with the scssLoaders being:

var scssLoaders = [   {     loader: 'css-loader',     options: {       modules: true,       importLoaders: '2',       localIdentName: '[name]__[local]__[hash:base64:5]'     }   },   {     loader: 'postcss-loader'   },   {     loader: 'sass-loader',     options: {       outputStyle: 'expanded',       sourceMap: true,       sourceMapContents: true     }   } ]; 

I'll just stop here before I go off about other problems. Can someone please help explain what I am missing here? Feel free to ask for any other code you need to help!

Thank you in advance.

like image 356
TwistedSt Avatar asked Jan 19 '17 20:01

TwistedSt


People also ask

When using webpack Why would you need to use a loader?

Webpack enables use of loaders to preprocess files. This allows you to bundle any static resource way beyond JavaScript. You can easily write your own loaders using Node. js.

What are module rules in webpack?

module.rulesAn array of Rules which are matched to requests when modules are created. These rules can modify how the module is created. They can apply loaders to the module, or modify the parser.

What is the difference between loader and plugin in webpack?

Loaders work at the individual file level during or before the bundle is generated. Plugins: Plugins work at bundle or chunk level and usually work at the end of the bundle generation process.

Do loaders work in a synchronous or an asynchronous way?

Loaders were originally designed to work in synchronous loader pipelines, like Node. js (using enhanced-require), and asynchronous pipelines, like in webpack. However, since expensive synchronous computations are a bad idea in a single-threaded environment like Node.


2 Answers

As the Webpack 2 migration tutorial states, the difference between both is, that if when we want an array of loaders, we have to use use, if it's just one loader, then we have to use loader:

module: {    rules: [       {         test: /\.jsx$/,         loader: "babel-loader", // Do not use "use" here         options: {           // ...         }       },       {         test: /\.less$/,         loader: "style-loader!css-loader!less-loader"         use: [           "style-loader",           "css-loader",           "less-loader"         ]       }     ]   } 
like image 131
Albert Olivé Avatar answered Oct 04 '22 23:10

Albert Olivé


module.rules is meant for loaders. Specifying a rule as loader is just a shortcut for

use: [{loader}] 

For plugins, use the plugins property in your configuration.

like image 28
simon04 Avatar answered Oct 04 '22 22:10

simon04