Loading...

Creating and Using Custom Events in Node.js

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

Why Long-Term IT Partnerships Outperform One-Off Project Vendors

A few months back, a CTO at a mid-sized NBFC told us something that stuck: “Every time we onboard a new vendor, we’re paying for the same discovery phase all over again.” His team had worked with four different development shops in three years, each one solving a narrow problem and then disappearing. The core […]

Choosing a Tech Partner Who Actually Understands Regulatory Compliance

A few months back, a fintech client came to us after a failed product launch. Their previous development partner had built a solid lending app — clean UI, fast performance, good UX. The problem? Nobody on that team had accounted for RBI’s Digital Lending Guidelines around data storage and third-party data sharing. The app went […]

How Automation Reduces Manual Errors in Banking Back-Office Work

A few months ago, we sat down with the operations head of a mid-sized NBFC who told us something that stuck with us: “My team isn’t lazy or careless. They’re just human, and humans reconciling 40,000 transactions a day will always slip somewhere.” That one sentence sums up why banking back offices keep bleeding money […]

Building Dashboards for Real-Time Transaction Monitoring: What Actually Works in BFSI

A few months back, one of our fintech clients — a Mumbai-based NBFC processing close to 40,000 UPI and card transactions a day — came to us with a problem that sounded simple on the surface: “Our fraud team is looking at data that’s 15 minutes old, and by the time they act, the money’s […]

Why a Dedicated PM Matters in Outsourced Software Projects (Especially for BFSI Teams)

A few months ago, a fintech client came to us at Speqto Technologies after a rough experience with a previous outsourcing vendor. The code wasn’t the problem — their developers were competent. The problem was that nobody owned the project end to end. Requirements got lost in Slack threads, QA found bugs three sprints too […]

POPULAR TAG

POPULAR CATEGORIES