You will need Node 6.11.5+ installed on your machine.

In the previous part of the series, we learned how to use Babel to compile JavaScript files written in ES6+ syntax. This will prove useful especially if we are trying to keep our codebase up to date but still supporting older browsers, which may not yet have ES6+ support.

In this part of the series, we will dig deeper into webpack to see what else is possible. We will specifically try to use webpack plugins. We will demonstrate how you can use plugins to make your webpack build better.

Let’s get started.

Source code of the application is available on GitHub.

Prerequisites

To follow along in this series, you need the following requirements:

Completed all previous parts of the series.

Basic knowledge of JavaScript.

Basic knowledge of the CLI.

A text editor. VS Code is recommended.

Node.js (>=6.11.5) and npm installed locally.

Let’s continue with the series.

Getting started with webpack plugins

At its core, webpack has very good support for plugins. The bundler itself has many internal components that are plugins. This means webpack itself makes use of the plugin system. What can plugins do?

Well it’s really up to the imagination what the plugins are capable of doing. As seen from their documentation, there are a lot of plugins available that do different things when activated. Let’s see the syntax for adding plugins to webpack.

Plugins are usually installed using npm and then added to the webpack configuration file so they can be used as a part of webpack’s bundling process. Here is an example of a webpack plugin being activated:

var HtmlWebpackPlugin = require ( 'html-webpack-plugin' ); var path = require ( 'path' ); module .exports = { entry : 'index.js' , output : { path : path.resolve(__dirname, './dist' ), filename : 'index_bundle.js' }, plugins : [ new HtmlWebpackPlugin()] };

In the code above, we are importing the html-webpack-plugin at the top and then in the plugins array, we are initializing the plugin. All plugins you intend to add to webpack have to be added to this array so they can be called when webpack is processing files. For example, if there are multiple plugins you would have something like this:

module .exports = { plugins: [ new HtmlWebpackPlugin(), new SomeOtherPlugin(), new YetAnotherPlugin(), ] }

Now that we know how to add and activate webpack plugins, you should also know that you can, based on the environment, load or ignore certain plugins. The webpack configuration file is just a JavaScript file, and thus, we can write pure JavaScript in it.

In this file, we have access to the process.env property. The process.env property returns an object containing the user environment. With this, we can easily access the NODE_ENV property and check what environment webpack is running on.

This is useful because we can decide to activate some plugins when building for the production environment and omit them when building for the development environment.

Conditionally loading plugins

As mentioned earlier, we can use the value from the process.env.NODE_ENV to conditionally load the plugins for webpack. Let’s see how this will look:

var HtmlWebpackPlugin = require ( 'html-webpack-plugin' ); var path = require ( 'path' ); module .exports = { entry : 'index.js' , output : { path : path.resolve(__dirname, './dist' ), filename : 'index_bundle.js' }, plugins : [] }; if (process.env.NODE_ENV == 'production' ) { module .exports.plugins.push( new HtmlWebpackPlugin() ) }

As seen above, we have an if statement that checks which environment webpack is run on and if it is development, we can then load the HtmlWebpackPlugin . This works with custom environments also not just development and production. For example, we can have this:

if (process.env.NODE_ENV == 'staging' ) { module .exports.plugins.push( new HtmlWebpackPlugin() ) }

Above, we are now only loading the HtmlWebpackPlugin if the environment is staging . You can manually set the environment webpack is running on by appending the following during the build command:

NODE_ENV=environment

For example, to run in production environment, you can run the following command:

$ NODE_ENV=production npm run build

This will first set the NODE_ENV to production and then it’ll run the command to build using the environment we specified.

Adding plugins to our project

For this part, we will be building off the code in part four of the series. If you don’t have it already, you can download the project code from GitHub. We will be using the code there as a base for the modifications we are going to make going forward. When you have downloaded the project, open Part-4 in your code editor and follow along.

Before we get started, run the following command in the root of the project to install the npm dependencies:

$ npm install

To get started, we need to decide the plugins we want to use and then install them using npm. After installing them, we will activate them in the webpack configuration file. We will conditionally load some of the plugins to demonstrate how you could do this in a real app.

The plugins we will use are as follows:

UglifyJS plugin - to minify the JavaScript bundle file when in production.

mini-css-extract-plugin - to extract our CSS into its own bundled file on any environment.

Optimize CSS asset plugin - to optimize and minify the CSS on production environment.

Let’s start adding the plugins one after the other.

UglifyJS webpack plugin

The first plugin we want to install and activate in the project is the UglifyJS plugin. We will be using this plugin to minify the outputted JavaScript. To install this package, run the following command in your terminal:

$ npm install --save-dev uglifyjs-webpack-plugin

When the installation is complete, you can then open the webpack.config.js file and replace the contents with the following code:

const webpack = require ( 'webpack' ); const path = require ( 'path' ); const UglifyJsPlugin = require ( 'uglifyjs-webpack-plugin' ); const env = process.env.NODE_ENV; module .exports = { mode : env == 'production' || env == 'none' ? env : 'development' , entry : path.resolve(__dirname + '/src/index.js' ), output : { path : path.resolve(__dirname + '/dist/assets' ), filename : 'bundle.js' }, module : { rules : [ { test : /\.scss$/ , use : [ 'style-loader' , 'css-loader' , 'sass-loader' ] }, { test : /\.js$/ , exclude : /node_modules/ , loader : 'babel-loader' } ] }, plugins : [], optimization : { minimizer : [] } }; if (env === 'production' ) { module .exports.optimization.minimizer.push( new UglifyJsPlugin()); }

Above, we imported the UglifyJsPlugin, then we updated the mode config property to be automatically set depending on the NODE_ENV set when running webpack. To activate the plugin however, we are not using the plugins array because webpack has an optimization property with a minimizer array. This is the place where we added our Uglify plugin.

Before activating the Uglify plugin though, we check if webpack is being run for a production environment.

Since we now have a production environment, let’s update the scripts in our package.json file to support production builds. Open the package.json and replace the code in it with the following:

// File: package.json { "name": "webpack-part-5", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "build": "webpack", "prod": "NODE_ENV=production webpack", "watch": "npm run build -- --watch" }, "keywords": [], "author": "", "license": "ISC", "devDependencies": { "@babel/core": "^7.2.2", "@babel/preset-env": "^7.2.0", "babel-loader": "^8.0.4", "css-loader": "^2.0.0", "node-sass": "^4.11.0", "sass-loader": "^7.1.0", "style-loader": "^0.23.1", "webpack": "^4.26.1", "webpack-cli": "^3.1.2", "uglifyjs-webpack-plugin": "^2.0.1" }, "dependencies": { "express": "^4.16.4" } }

If you are using a Windows machine, read here before continuing.

Above, we have added the new prod build script. This makes it so we are running webpack in a production environment anytime we run the command below:

$ npm run prod

To build our script and see if it works, run the following command:

$ npm run prod

This should generate a minified JavaScript file in dist/assets/bundle.js . If you run the other command:

$ npm run build

Then you should see an unminified JavaScript bundle file.

Next, let’s install the other dependencies:

$ npm install --save-dev mini-css-extract-plugin optimize-css-assets-webpack-plugin

When the installation is complete, open the webpack.config.js file and replace the contents with the following code:

const webpack = require ( 'webpack' ); const path = require ( 'path' ); const UglifyJsPlugin = require ( 'uglifyjs-webpack-plugin' ); const MiniCssExtractPlugin = require ( 'mini-css-extract-plugin' ); const OptimizeCssAssetsPlugin = require ( 'optimize-css-assets-webpack-plugin' ); const env = process.env.NODE_ENV; module .exports = { mode : env == 'production' || env == 'none' ? env : 'development' , entry : path.resolve(__dirname + '/src/index.js' ), output : { path : path.resolve(__dirname + '/dist/assets' ), filename : 'bundle.js' }, module : { rules : [ { test : /\.scss$/ , use : [MiniCssExtractPlugin.loader, 'css-loader' , 'sass-loader' ] }, { test : /\.js$/ , exclude : /node_modules/ , loader : 'babel-loader' } ] }, plugins : [ new MiniCssExtractPlugin({ filename : '[name].css' , chunkFilename : '[id].css' }), new OptimizeCssAssetsPlugin({ cssProcessorPluginOptions : { preset : [ 'default' , { discardComments : { removeAll : true } }] } }) ], optimization : { minimizer : [] } }; if (env === 'production' ) { module .exports.optimization.minimizer.push( new UglifyJsPlugin() ); }

Above, we have added both the MiniCssExtractPlugin and the OptimizeCssAssetsPlugin to the webpack configuration. These two plugins will make sure the CSS is extracted to its own file and minified so it has a smaller size.

Now let’s see if our plugins work. Open your terminal and run the following command:

$ npm run prod

If all goes well, you should have a new main.css file in the dist/assets folder. The CSS should be minified.

Quick gotcha

Webpack comes with uglification bundled automatically. When you set the mode to production , all JavaScript code will be minified automatically. With this knowledge, you can remove all the references to the UglifyJsPlugin in the code as we do not need it.

Previewing our application

To preview the app with the new changes, we need to update a few files. Open the dist/index.html file and replace the contents with the following:

< html lang = "en" > < head > < meta charset = "UTF-8" /> < meta name = "viewport" content = "width=device-width, initial-scale=1.0" /> < meta http-equiv = "X-UA-Compatible" content = "ie=edge" /> < title > Webpack Sample </ title > < link rel = "stylesheet" href = "/assets/main.css" /> </ head > < body > < div class = "container" > < h1 > </ h1 > </ div > < script src = "./assets/bundle.js" > </ script > </ body > </ html >

In the code above, we just added a link to the CSS file that we know will be generated by webpack.

Next, open the dist/server.js and replace the contents of the file with the following:

const express = require ( 'express' ); const app = express(); const port = 3000 ; const path = require ( 'path' ); app.get( '/assets/bundle.js' , (req, res) => res.sendFile(path.join(__dirname + '/assets/bundle.js' ))); app.get( '/assets/main.css' , (req, res) => res.sendFile(path.join(__dirname + '/assets/main.css' ))); app.get( '/' , (req, res) => res.sendFile(path.join(__dirname + '/index.html' ))); app.listen(port, () => console .log( `Example app listening on port ${port} !` ));

Above, we added a new route to handle the serving of the CSS asset file. That’s all. Now run the following command to start the Node.js server:

$ node dist/server.js

When the app is running, you can see it at http://localhost:3000.

Conclusion

In this part of the series, we have learned how use plugins in webpack. We also learned about optimizations in webpack and how we can use some plugins as minimizers. However, webpack is a lot more powerful than this. We will dive a little deeper in the next part.

The source code to this application is available on GitHub.