Skip to main content

Understanding EventEmitter in Node.js With a UseCase

One of the core concepts of Node.jsis events. Event Emitter plays a vital role in Node.js Event-Driven Architecture

Event Emitter is a module that facilitates communication between objects in Node.js. Most of the Libraries/Modules built on Node.js uses EventEmitter Since Node.js follows the Event-Driven Architecture.

That is to say, we will learn Event Emitter by building a custom logger using Event Emitter in this article.

How does it work?

  • Event Emitter emits the data in an event called message
  • A Listened is registered on the event message
  • when the message event emits some data, the listener will get the data.

eventEmitter works

Building Blocks

  • .emit() - this method in event emitter is to emit an event in module
  • .on() - this method is to listen to data on a registered event in node.js
  • .once() - it listen to data on a registered event only once.
  • .addListener() - it checks if the listener is registered for an event.
  • .removeListener() - it removes the listener for an event.

eventemiitter

1const EventEmitter = require("events")
2
3const emitter = new EventEmitter()
4
5emitter.on("message", function(message) {
6 console.log("subsribed", message)
7})
8
9emitter.emit("message", { data: "Data" })

Firstly, import the package called events which is basically a class. After that, instantiates the class with a name emitter.

After that, we need to register the listener for the particular event.

Finally, when if we emit an event, the registered listener will get the event along with the data.

Use-Case

As I said earlier, event emitter is an important concept in node.js. we learned how it works and important building blocks of it.

But, One of the important questions that come to our mind when we learn something is, where do I need to implement that?.

Let's see a use-case to understand more about Event-Emitters.

Logger using Event Emitter

Mainly, we will see how to write a logger function using Event Emitter.

create a file called logger.js and add the following code.

1const EventEmitter = require("events")
2
3class Logger extends EventEmitter {
4 logIt(eventName, message) {
5 this.emit(eventName, message)
6 }
7}
8
9module.exports = Logger

class Logger extends the EventEmitter class. add the following method called logIt which takes event name and message as an argument.

create a file called an index.js and add the following code.

1const Logger = require("./Logger")
2
3const logger = new Logger()
4
5logger.on("logMessage", arg => {
6 console.log("Listened value => ", arg)
7})
8
9logger.logIt("logMessage", { name: "John", age: 40 })

it requires the module Logger and instantiates the class as a logger.

logIt() function emits event called logMessage. the listener will listen for the event and log it.

Comments

Popular posts from this blog

How to use Ngx-Charts in Angular ?

Charts helps us to visualize large amount of data in an easy to understand and interactive way. This helps businesses to grow more by taking important decisions from the data. For example, e-commerce can have charts or reports for product sales, with various categories like product type, year, etc. In angular, we have various charting libraries to create charts.  Ngx-charts  is one of them. Check out the list of  best angular chart libraries .  In this article, we will see data visualization with ngx-charts and how to use ngx-charts in angular application ? We will see, How to install ngx-charts in angular ? Create a vertical bar chart Create a pie chart, advanced pie chart and pie chart grid Introduction ngx-charts  is an open-source and declarative charting framework for angular2+. It is maintained by  Swimlane . It is using Angular to render and animate the SVG elements with all of its binding and speed goodness and uses d3 for the excellent math functio...

Understand Angular’s forRoot and forChild

  forRoot   /   forChild   is a pattern for singleton services that most of us know from routing. Routing is actually the main use case for it and as it is not commonly used outside of it, I wouldn’t be surprised if most Angular developers haven’t given it a second thought. However, as the official Angular documentation puts it: “Understanding how  forRoot()  works to make sure a service is a singleton will inform your development at a deeper level.” So let’s go. Providers & Injectors Angular comes with a dependency injection (DI) mechanism. When a component depends on a service, you don’t manually create an instance of the service. You  inject  the service and the dependency injection system takes care of providing an instance. import { Component, OnInit } from '@angular/core'; import { TestService } from 'src/app/services/test.service'; @Component({ selector: 'app-test', templateUrl: './test.component.html', styleUrls: ['./test.compon...

How to solve Puppeteer TimeoutError: Navigation timeout of 30000 ms exceeded

During the automation of multiple tasks on my job and personal projects, i decided to move on  Puppeteer  instead of the old school PhantomJS. One of the most usual problems with pages that contain a lot of content, because of the ads, images etc. is the load time, an exception is thrown (specifically the TimeoutError) after a page takes more than 30000ms (30 seconds) to load totally. To solve this problem, you will have 2 options, either to increase this timeout in the configuration or remove it at all. Personally, i prefer to remove the limit as i know that the pages that i work with will end up loading someday. In this article, i'll explain you briefly 2 ways to bypass this limitation. A. Globally on the tab The option that i prefer, as i browse multiple pages in the same tab, is to remove the timeout limit on the tab that i use to browse. For example, to remove the limit you should add: await page . setDefaultNavigationTimeout ( 0 ) ;  COPY SNIPPET The setDefaultNav...