Node.js TypeScript #2. The synchronous nature of the EventEmitter

JavaScript Node.js

This entry is part 2 of 15 in the Node.js TypeScript

In this article, we continue going through the main concepts connected to Node.js. This time we dive into the idea of the Node.js EventEmitter. We explain its synchronous nature and how it works, which helps with understanding other Node.js features because some of them use the EventEmitter under the hood.

Node.js TypeScript: EventEmitter

Using events is a big part of working with JavaScript and therefore. A lot of Node.js core depends on event-driven architecture. Because of it, a lot of objects that you can encounter inherit from the EventEmmiter.

Certain objects can emit events and we call them emitters. We can listen to those and react in a way using callback functions called listeners.
An instance of the EventEmmiter has a method “on” that allows one or more function to be attached to an object.
The instance of the EventEmmiter also has a method “emit” that emits an event and causes all the EventEmitter to call all the listeners.


The EventEmitter called all of the above functions synchronously. If you look into the Node.js source code, you can confirm that they run in an order that they were attached.

The “on” function is an alias for “addEventListener” and both functions act the same way

You can also observe that if you attach a listener after you call the emit function, the EventEmitter does not call it.

It is an important thing to keep in mind especially if you are more familiar with promises. It is due to the fact that with promises you can add callbacks long after a promise is resolved and it is going to be called immediately.

If you want to know more about promises, check out Explaining promises and callbacks while implementing a sorting algorithm

Passing additional data to listeners

The emit function allows you to send arguments to the listener functions. Inside of a listener function, the “this” keyword refers to the instance of the Event Emitter:

A lot of event emitters that you encounter pass additional arguments to listeners.

If you use the arrow functions here, the “this” keyword no longer references to the Node.js EventEmitter instance.

This behavior is caused by the way that arrow functions behave. If you want to know more check out What is “this”? Arrow functions

Removing listeners

If you don’t want the EventEmitter to invoke a listener anymore, you can use the removeListener function. By calling it, you remove the listener from a particular event. To do that, you need to provide the removeListener function with the name of the event, and the reference to the callback function.

Please note that if you added more than one instance of a listener, you need to remove it more than once to get rid of it. You can also use the removeAllListeners function to remove all listeners for a particular event.

The synchronous nature of events

As said above, Node.js EventEmmiter calls all listeners synchronously. We can observe it by calling them into one another:

After a bunch of messages in the console, you encounter an error:

Maximum call stack size exceeded

The error is thrown because the actual execution of the above listeners looks like this:

The event emitter executes all callbacks in a synchronous manner. Every time you call a function, its context is pushed on the top of the call stack. When the function ends, the context is taken off from the stack. If you call one function inside of the other, the data can pile up in your call stack and eventually cause it to overflow.

I dive deeper into this context in Using recursion to traverse data structures. Execution context and the call stack

You can change this behavior a bit by using, for example, the setTimeout function. When the Node.js interprets the setTimeout function, it sets off a timer. When it goes off, it throws the callback to the end of the event loop. Due to that, one function is not called inside of the other one and the call stack is not exceeded.

We explain the event loop a lot more in future parts of the series, but you can also check out When async is just not enough. An introduction to multithreading in the browser, where I explain this concept a bit in the context of comparing asynchronous functions and multithreading.

Handling events just once

When you register the listener using the “on” or “addEventListener” methods, the Node.js EventEmitter invokes it every time it emits the event.

If instead of the “on” function you use “once,” you register a listener that the EventEmitter calls not more than once for a particular event.


In this article, we went through the most essential features of the Node.js EventEmitter. It is due to the fact that it is widely used in other core features of Node.js. We encounter it as we go through other important concepts like the streams in upcoming parts of the series, so stay tuned!

Series Navigation<< Node.js TypeScript #1. Modules, process arguments, basics of the File SystemNode.js TypeScript #3. Explaining the Buffer >>
Notify of
1 Comment
Newest Most Voted
Inline Feedbacks
View all comments
Ashish Bagaddeo
5 years ago

Great Article👍👍