Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
tavo glz
Web Developer spending each day wrangling front and back-end code - helping keep Genuitec on the web.
Contributions by Jose Ruiz

Webpack is an open-source JavaScript module bundler developed by Tobias Koppers and Webpack contributors. The initial release was March 10th, 2012 and the current stable version is 1.13.

Webpack takes modules with dependencies and generates static assets representing those modules. All your assets are considered as modules and packaged in a final bundle with the rest of your modules. In order for this to work, you must register each loader in the webpack configuration, telling it what it must do when finding a specified file. Loaders are little plugins that transpile files (e.g., Babel for ES6 code to vanilla ES5; style, css, sass, html, and typescript are some other loaders).

In big projects it is not recommended, nor efficient, to put all code in a single file. This is especially true when some blocks of code are only necessary in certain circumstances. Webpack includes a code splitting feature that splits your base code in chunks or fragments that are loaded on demand in your app. This keeps a small initial load, and downloads code on demand when requested for the app. You don’t have to think about what to merge, when or where. If a chunk starts having more dependencies, the chunk is moved to an async chunk instead of being merged; and if these chunks start looking too similar to be worth loading separately, they are merged. You just set up the rules, and from then on, Webpack will automatically optimize your application in the best way possible.

Installing Webpack

Webpack requires Node.js. To install it we are going to need NPM. Install it with the following command:

npm install webpack -g

The –global or -g option installs this module globally so that you can run it as a command in your terminal.


Create a simple sample project to verify everything is working fine. First, create a folder. I called mine webpack-sample. Use the following command to initialize the project:

npm init -y

It creates a package.json file:

Note: You might want to to add the private attr true to the package.json so this module can never be uploaded to a public NPM module.

Next, let’s add the Webpack dependency:

npm install webpack --save-dev

–save-dev indicates that library will be added as dependency on our package.json.

Let’s say this is our app’s code:




So the first requirement to pack our files is to modify them to meet the Common.js specification:


After that we create a new app.js file that will import the others following the Common.js specification:

The final step is to create the config webpack file, webpack.config:

Run the webpack command to generate the bundle file:

octavio@pc:~$: webpack

Refactor the index.html file and open it to see it does the same:

Loaders: A Practical Example

Let’s say we’re building our Genuitec site and adding to main sections of our MyEclipse and SDC products. We want all of our pages to share the same header but the menu below will change depending on the section. How is Webpack going to help us here? Well, consider that after adding many pages, are we going to paste the code of our <header>…</header> in all of them? And if we make a typo? The best option is for all pages to use the same code.

Also, Webpack will help us to load only the stylesheets needed by the current page, as well as the corresponding JavaScript files. This might sound confusing, but after finishing the example it will be clear.

Creating the Project

The first step is to create a new folder and initialize our project.

npm init -y

This creates the /package.json file with our npm package config and dependencies.

Then we proceed to install the webpack module and jquery as we’re going to use it. The –save-dev option tells Webpack that it must even include the library as development dependencies in the package.json file.

npm install jquery --save-dev
npm install webpack --save-dev

Now we create a /webpack.config.js to specify our input files and our output files and path. Also, we need to add which modules will be used. Our config file should look like this:

Note in module property we have a loaders objects array that will process our files in src directory. Notice that the HTML loader, as the name says, will process the HTML files and the Babel loader will take care of our JS files written in ES6.

Before continuing, we must install these modules or we’ll have trouble compiling our project with Webpack.

HTML loader

npm install html-loader --save-dev


npm install babel-loader --save-dev

Babel Core

npm install babel-core babel-preset-es2015 --save-dev

We need to create a .babelrc file to process our ES6 code with the following code:

{ "presets": ["es2015"] }

Now we’re going to create our main js file in the src folder.


Header Component

The next step is creating the template of our Header “component”:


And our component JavaScript file:


We can see that a Mustache function was called to render our template. So we install this plugin/loader as well:


npm install mustache --save-dev

The final step is creating our index.html file that will load our generated bundle.js file in the project root folder:


And we’re ready to see how our first component is packed. Run the webpack command and you should see something similar to this:


Open the index file in the browser and you will see the Header was appended to body:


But, what if we want to add an image to our header and a little CSS magic? Well, that’s easy by adding a couple of loaders.

CSS and style loader

npm install css-loader style-loader --save-dev

Url and file loaders

npm install url-loader file-loader --save-dev

And then we need to include these in our webpack.config.js:

Our final config should be like this:

Note that also was added a property publicPath to the output property.

Now we can modify our Header component to include an image and add some CSS.



Then we need to modify a little bit our index file, deleting the content in the anchor, so our Header.html file should look like this:


Running the webpack command again we’ll see the result:


Now, we’re going to add other pages for the SDC and ME products. Each one of these pages has its own menu and we don’t want to load the resources of SDC when the ME page is loaded and vice versa.

The first thing we need to do is to create the main file for each product so these can be called from the browser.



As we can see, there is a specific class in the body label for each product page that allows it to recognize the page where each menu is displayed.

Now, let’s create three little files for each product page, one for CSS code, another for Javascript code and one more for a partial template code.

Let’s start with the SDC product page and create the HTML template in a file named SDC_Menu.html in the Components folder, as shown below:


This file contains an unsorted list with some links–it will be a menu for the SDC product with a little help from CSS.


And now, our JavaScript file to export the component:


Now we can add the code needed to render the SDC menu when the “sdc_product” class is present.


Everything in the require.ensure callback would be split into a chunk – a separate bundle that Webpack will load only when needed, through an AJAX request. So if we execute the webpack command to apply the changes, we will see something like this:


The main bundle, bundle.js, contains the header with the company logo and 1.bundle.js is a chunk with the code needed to render the SDC menu. It is only loaded in the sdc.html page but not in the index.html page, as we can see below:





Now, we just need to repeat the same process to add the ME page with its own menu.




And append a new require.ensure in the index.js file to create a chunk for the resources of this page:


Now when we execute webpack we see a new bundle named 2.bundle.js that will be loaded in the me.html page:





Although our project is small, it will grow as we add more functionality. There is a tool to analyze our build and give us hints about how to optimize its size and performance.

We can generate the required JSON file by running:

webpack --profile --json > stats.json

and then import in the tool.


Attachment—Sample project

Let Us Hear from You!

If you have any comments or questions, we would love to hear from you @MyEclipseIDE on twitter or via the MyEclipse forum. Happy coding!

If you’re not already subscribing to our blogs, why not do it today?


Related Posts

Angular 5 Authentication: Getting Started In this tutorial, we are going to build an Angular 5 authentication system using Google’s Cloud Firestore. Most of the applications we build require some kind of authentication, and the simplest and fastest way to get started with that is by using the Firestore - a flexible, scalable database for mobile, web and server development. You will learn t...
Introducing DevStyle – Rebooting EclipseR... Yesterday we released the first production version of DevStyle, a free add-on for Eclipse. DevStyle seeks to dramatically improve the Eclipse user experience for millions of developers with the introduction of modern developer ergonomics and the beautiful styling you’ve come to expect from products in 2017.Over the years, the Eclipse evolution has ...
Gradle vs Maven – in Search for the Perfect ... In your quest for the perfect build automation tool, you have probably come across Maven and Gradle - the two big players in the field. The decision here is no less tricky than picking just the right ingredients for that awesome holiday dish you might be thinking about preparing. Of course, each tool has its advantages and downsides, depending on y...
Set Up and Use a Fake REST API with Angular Often, when developing Angular applications, you do not have the backing REST APIs ready for testing. To avoid having to digress into developing web services, or being blocked, waiting for your back end team to provide them, you can use JSON server to provide a "fake" API. This article will show you how to use Angular IDE and JSON Server to set up ...

Posted on Jul 14th 2016