Loading...

Creating and Using Custom Events in Node.js

Jeevan Singh

27 October, 2025

Node.js Logo


Node.js is built around an event-driven architecture, which makes it incredibly efficient for handling asynchronous operations. Events are at the core of Node.js — they allow you to execute code when specific actions occur. While Node.js provides many built-in events (like request and connection), you can also create your own custom events to make your applications more modular and interactive.

What Are Events in Node.js?

An event in Node.js is a signal that something has happened in your application. For example, when a server receives a request, an event is triggered.
Node.js uses the EventEmitter class from the events module to handle such event-driven behavior.

Why Use Custom Events?

Custom events make your code cleaner, more organized, and easier to maintain. They are particularly useful when:

  • You want to separate logic between components.
  • You need to notify different parts of your app when an action occurs.
  • You’re working with asynchronous operations that depend on specific triggers.
  • You want to create modular, reusable systems that communicate via events.

The EventEmitter Class

The EventEmitter class in Node.js is the foundation for handling and creating custom events. It allows you to:

  • emit an event — trigger it.
  • on or addListener — listen for when the event occurs.
  • once — listen for the event only one time.
  • removeListener — stop listening to an event.

To use custom events, you first need to import this class and create an instance of it.

Example: Creating and Listening to a Custom Event

Here’s a simple example to demonstrate how to create and trigger your own event:

const EventEmitter = require('events');

// Create an instance of EventEmitter
const eventEmitter = new EventEmitter();

// Define a custom event
eventEmitter.on('greet', (name) => {
  console.log(`Hello, ${name}! Welcome to Node.js events.`);
});

// Trigger (emit) the custom event
eventEmitter.emit('greet', 'John');

In this example:

  • We created a custom event called greet.
  • We used on() to listen for the event.
  • We used emit() to trigger the event and pass data (“John”).

Using Multiple Listeners

You can also attach multiple listeners to the same event:

const EventEmitter = require('events');
const eventEmitter = new EventEmitter();

eventEmitter.on('status', () => console.log('Task started!'));
eventEmitter.on('status', () => console.log('Task in progress...'));
eventEmitter.on('status', () => console.log('Task completed!'));

eventEmitter.emit('status');

When emit('status') is called, all listeners attached to the status event are executed in order.

Using once() for One-Time Events

If you want an event listener to run only once, you can use the once() method:

const EventEmitter = require('events');
const eventEmitter = new EventEmitter();

eventEmitter.once('connect', () => {
  console.log('Connected successfully! This message appears only once.');
});

eventEmitter.emit('connect');
eventEmitter.emit('connect'); // Won’t run again

This is useful for tasks like initializing a database connection or logging one-time startup messages.

Passing Data with Events

You can pass any number of arguments to your event listeners via emit():

eventEmitter.on('order', (item, price) => {
  console.log(`Order placed for ${item} costing $${price}`);
});

eventEmitter.emit('order', 'Laptop', 1200);

This flexibility allows you to send relevant data dynamically whenever the event is triggered.

Removing Event Listeners

If you no longer need a listener, you can remove it using removeListener() or removeAllListeners():

const greet = (name) => console.log(`Hello, ${name}!`);
eventEmitter.on('greet', greet);

eventEmitter.removeListener('greet', greet);
eventEmitter.emit('greet', 'John'); // No output since listener removed

Real-World Example: File Upload Notification

Custom events are extremely useful in real-world applications. For example:

const EventEmitter = require('events');
const eventEmitter = new EventEmitter();

function uploadFile(filename) {
  console.log(`Uploading ${filename}...`);
  setTimeout(() => {
    eventEmitter.emit('uploadSuccess', filename);
  }, 2000);
}

eventEmitter.on('uploadSuccess', (file) => {
  console.log(`File "${file}" uploaded successfully!`);
});

uploadFile('profile-picture.png');

Here, the uploadFile() function triggers a custom event after the simulated upload completes, and another part of the app listens for that event to perform follow-up actions.

Conclusion

Custom events make Node.js applications more modular, scalable, and easier to manage. By using the EventEmitter class, you can define custom triggers and listeners that communicate between different parts of your app seamlessly.
Whether you’re building APIs, file systems, or chat applications, mastering custom events is an essential step toward writing cleaner and more efficient Node.js code.

RECENT POSTS

From First Call to Project Launch — A BD’s Guide to Seamless Client Onboarding

From First Call to Project Launch — A BD’s Guide to Seamless Client Onboarding Chirag Verma 29/10/2025 In the IT industry, a client’s first impression can define the entire relationship. From the very first call to the moment a project officially begins, every step of the onboarding journey shapes how the client perceives your company’s […]

Understanding Event Loop & Async Behavior in Node.js

Understanding Event Loop & Async Behavior in Node.js Divya Pal 26 September, 2025 Node.js is known for its speed and efficiency, but the real magic powering it is the Event Loop. Since Node.js runs on a single thread, understanding how the Event Loop manages asynchronous tasks is essential to writing performant applications. In this blog, […]

REST vs GraphQL vs tRPC: Performance, Caching, and DX Compared with Real-World Scenarios

REST vs GraphQL vs tRPC: Performance, Caching, and DX Compared with Real-World Scenarios Shubham Anand 29-Oct-2025 API architecture selection—REST, GraphQL, and tRPC—directly impacts an application’s performance, caching, and developer experience (DX). In 2025, understanding how each performs in real-world scenarios is critical for teams seeking the right balance between reliability and agility. 1. REST: The […]

Collaborating in a Multi-Disciplinary Tech Team: Frontend and Beyond

Collaborating in a Multi-Disciplinary Tech Team: Frontend and Beyond Gaurav Garg 28-10-2025 Cross-functional collaboration is a force multiplier for product velocity and quality when teams align on shared goals, clear interfaces, and feedback loops across design, frontend, backend, DevOps, data, and QA. High-performing teams in 2025 emphasize structured rituals, shared artifacts (design systems, API contracts), […]

The Role of a BDE in Helping Businesses Modernize with Technology

The Role of a BDE in Helping Businesses Modernize with Technology Karan Kumar 28/10/2025 At Speqto Technologies, we’ve witnessed firsthand how technology has become the foundation of business success in 2025. But adopting new technologies isn’t just about staying trendy it’s about staying relevant, competitive, and efficient. That’s where a Business Development Executive (BDE) plays […]

POPULAR TAG

POPULAR CATEGORIES