Node.js Lesson 12: HTTP Module and Nodemon

Node.js Lesson 12: Documentation of HTTP Module and Nodemon

Node.js Lesson 12: Documentation of HTTP Module and Nodemon

Hey everyone, today we will dive deeper into the HTTP module and learn it’s functionality. We will learn about what are the function provided that can be helpful and how to use them. We will also learn about Nodemon and improve our development process. Let’s start.

HTTP module provides us with a bunch of functions, let’s take a look at each one by one.


After loading the http module with the required function, we can use http.createServer() to create a new object of the Server class.

This server object is an event emitter so all the methods available to event emitter are available on this object, for example, server.on(), server.addListener(), server.listen(), etc. If you remember from earlier lessons, we were using server.listen(port) to listens to requests to a particular port.

http.createServer() also takes a functions with arguments request and response. Let’s talk more about request and response.

Request and Response

They are emitted whenever a new request comes to the server. request and response objects are the first and second arguments of the callback function passes the createServer method respectively.
request is an instance of IncomingMessage class and is used to get info about the incoming requests like URL, query params, etc.
response is an instance of ServerResponse class and has multiple methods associated with response like setHeader, send, end, etc. We can use these methods to curate an outgoing response before sending.

Whenever a request is received, the request event happens and control is delivered to the handler function which we just talked about in the above paragraph. An IncomingMessage object is created by http.Server or http.ClientRequest and passed as the first argument to the ‘request‘ and ‘response‘ event respectively. It may be used to access response status, headers, and data.

When you are aware of the type of request, we move on to dealing with how to serve it. Here come the ServerResponse class instance passes as a response object. It enables us with functionalities like setting status code, headers, adding a message, etc, and send the response. We prepare the response and send it back to the client. This is what we generally refer to as nodejs lifecycle. Let’s talk about that with more clarity.

Nodejs Lifecycle

Nodejs is an event-based platform, everything that happens is in reaction to an event. Keep this in mind and let’s understand how the node lifecycle works. Javascript is single-threaded means everything runs on a single thread. Nodejs can execute this many requests asynchronously because of a concept called EventLoop. We will learn about the event loop in detail in further lessons but for now, you can consider it juggling through various phases of operations needed to serve a request in a loop fashion. All requests don’t have to be in one phase at a time and they all can be served separately. Nodejs uses a callback mechanism where one request calls the operation back to it once it is done processing while other requests are ready to be served.

In short, the whole lifecycle looks like this: Node app boots up and starts executing the script. It starts listening to a port and registers the event. Since we are using event emitter, we instantly get to know whenever a request arrives. The requests enter the event loop and it keeps running until the request is complete. We can exit this loop by calling process.exit() and the node will stop running. But we don’t often do that because we want to keep listening to the requests. I hope you’re able to get some idea about how the whole thing is working. If you’re not, don’t worry. We will learn the whole EventLoop concept again in the upcoming lessons.

To learn more about HTTP module, visit nodejs documentation.

Improve Nodejs development experience

Right now, the node server stops running as soon as it encounters an error. We have to start the server again whenever we do some changes to our code. This looks okay but it is not very productive. Luckily, there is a package that helps us restart the server automatically as soon as we change the code. This improves the whole development experience and reduces our development time by a lot. The package is Nodemon. Let’s install Nodemon and learn how to set up it.

How to setup Nodemon

Nodemon is a CLI utility that we can install globally and use with any project locally. It simplifies the whole development workflow so that we don’t have to start the server every time we make any change to the source code. To install Nodemon, enter this command in the terminal.

if you’re using yarn

You can also it install locally, you will have to install it as dev dependency by adding –save-dev instead of -g. For yarn, it’s -dev instead of global.

You have all the powers of Nodemon now and you can start the server by using this command:

Nodemon is like a wrapper to your node application. It means you can do everything that you will eventually do with node CLI only. This also includes passing arguments while running your app.

That’s it. You have completed the Nodemon setup and this will eventually save a lot of development time. We are done with today’s lesson, let’s meet again with a new lesson in Nodejs.

About the author

Stay Informed

It's important to keep up
with industry - subscribe!

Stay Informed

Looks good!
Please enter the correct name.
Please enter the correct email.
Looks good!

Related articles


Interoperability between Ethereum, Binance Smart Chain, and other blockchain platforms using Node.js

In this article, I will deeply into the importance of interoperability in the blockchain sphere and present use cases that support this perspective. ...


Anime.js to MP4 and GIF with Node.js and FFMPEG

While canvas animation is often considered the simpler approach for exporting animations to video and GIF formats, it can also limit the range of ...

Node.js Lesson 17: Timers, Differences from Browser, ref and ref

Hey, guys! Our today’s article will tell you about Node.js timers. Here we will try to tell you about all the differences existing between browser ...

No comments yet

Sign in

Forgot password?

Or use a social network account


By Signing In \ Signing Up, you agree to our privacy policy

Password recovery

You can also try to

Or use a social network account


By Signing In \ Signing Up, you agree to our privacy policy