Webpack 4 course – part one. Entry, output and ES6 modules

JavaScript Webpack

Hello! Today we begin a webpack 4 course. We will start with the basic concepts of Webpack, with every part of the course going deeper. This time we will learn the basics of module bundling using ES6 modules. Webpack 4 provide default configuration, which we will go through. Let’s go!

Webpack 4 course begins – but what is Webpack?

Before considering using any kind of tool, you need to ask yourself a very important question. The question is, what problem of yours does the tool solve. Webpack is a module bundler. It means, that its purpose is to merge a group of modules (with their dependencies). The output might be one, or more files. Aside from bundling modules, webpack can do all sorts of things with your files: for example transpile scss to css, or typescript to javascript. It can even compress all of your image files! But why would you want to bundle modules at all?

The purpose of module bundling

Way back in the days, we didn’t have any way of splitting our JavaScript code served for browsers into multiple files other than using many  tags. We needed to write a source of every file that we would like to use into the HTML code. It isn’t really convenient. The community came up with some workarounds: CommonJS (implemented into Node.js) and AMD. For an explanation of them, check out an article on the Auth0 blog. Finally, the ES6 came with a brand new import/export syntax.

ES6 modules

With the ES6, the syntax of modules was defined. Thanks to that, we finally got a standard format for modules, built into the JavaScript language specification. It does not mean that it is well implemented in browsers, but it is improving. Even with native support for ES6 modules, you still might want to bundle your modules into fewer files. For the purpose of the course providing all the information that you need to start using Webpack, let’s briefly go through the syntax of ES6 modules.


The export statement is used to create JavaScript modules. You can use it to export both objects (including functions) and primitive values. An important thing to notice is that exported modules are in strict mode. There are two types of export: named and default.

Named exports

You can have multiple named exports per module.


Note that if you would like to export something after its declaration, you need to wrap it in curly brackets (like the divide function in the example above).

Default exports

You can only have one default export per module.



The import statement is used to import from other modules.

whole module’s content


You can set any name you want for the imported module. If you are importing whole content from a module, that has a default export, it will be placed into a default property.


importing one, or more named exports


An important note is that the names of corresponding values must match.

importing a default export


Note, that the default export can be imported with any name, so we could do something like that:


The ES6 modules feature also dynamic imports, which we will get to in the future parts of the course.

Check out the MDN web docs for more examples of exports and imports.

Basic concepts of webpack

Since version 4, webpack does not require any configuration. It has a set of defaults. If you want to create a configuration file, you need to name it  . We will now mimic its default configuration to explain the basic concepts connected to Webpack.


Note that we write the webpack configuration file in Node.js, therefore it uses CommonJS type of modules.

The   exports a single object. If you run webpack through the console, it is going to look for that file and use it.


Webpack needs an entry point. It indicates which module webpack should use to begin the module bundling. The default is as follows:


It means that webpack will go to the  file and start the bundling from that. If you use any imports in the  file, webpack will handle them.

You can have more than one entry point, but with single page applications, it is common to have only one.


The output is a configuration of where webpack should output your bundle. It defaults to the   file.


Running webpack

In the sections before, we created the  file that imports functions from . Let’s finally run webpack! Remember to put those files into the  directory, so that it would match the default configuration.

The first thing you need to do is to install Webpack. I will be using npm for that. Fire up your terminal and write:

This will create a directory  with webpack in it, and two files:  and  .

If you would like to know more about dependencies in npm and the package-lock.json file, check out Keeping you dependencies in order when using npm

Now open the package.json file and modify your scripts:

Thanks to that, running   will use webpack from the   directory.

You can see that a file   was created in the   directory. It contains all your code both from the  and  files

Multiple entry points

You can achieve all of the above without any config file. If you would like to do some more, now it is a time to create it.


The entry property of our configuration does not have to be a string. If you would like to have multiple entry points, you can use an object.


With that code, we’ve created two entry points. It might be needed if you are developing a multi-page application.


There is an issue though: by default, there is only one output file specified. We can easily fix that:


With the code above, we indicate that there might be more than one file as the output. All files will have a distinct name now and will be called   and  , just like our entry points.

If you run webpack the same way as before, it will find the  file and apply the configuration.


Today we’ve learned the basics of module bundling with webpack using the ES6 modules. Webpack 4 provides default configuration, which we went through today while explaining the core concepts like the entry and output. Of course, Webpack can do much more than that. In the upcoming parts of the course, we will cover loaders, and even write one ourselves. Stay tuned!

Series NavigationWebpack 4 course – part two. Using loaders to handle scss, image files and transpile JS >>
Notify of
Newest Most Voted
Inline Feedbacks
View all comments
cloud confusing
5 years ago

Good read. A bit basic for some of us with experience in the space but this did clarify a few points, especially for us who have left webpack and are thinking about returning for v4

bob dobbs
bob dobbs
4 years ago

The webpack.config.js file doesn’t seem to meet the spec.

This line:
path: path.resolve(__dirname, ‘dist’)

… yields this error:
ReferenceError: path is not defined

4 years ago
Reply to  bob dobbs

path is a built in nodejs module you have to import it at the top of the file
const path = require(“path”)

4 years ago

Multiple entry points -> I have variables and functions in first.bundle.js – loaded in my root page – I call these functions in my second.bundle.js on another PAGE … I am getting errors … concerning my functions -> this is no function – cause second.bundle.js does not communicate with first.bundle.js … If I compile all js/css code in ONE bundle – all functions are working fine … HOW can I solve this?
Thank you in advance!
I hope you know a solution!
TC John

4 years ago

I love your content, very useful, thanks a lot !

4 years ago

Thanks to that, running npm run build will use webpack from the node_modules directory.

I believe that one must install webpack-cli first.

3 years ago