Browser Event Mechanisms: EventTarget vs EventEmitter

Event handling is a crucial task in frontend development. JavaScript offers various mechanisms for event handling, among which two common approaches are through the EventTarget interface in browsers and the EventEmitter class in Node.js. This article will delve into the principles, usage, and pros and cons of these two mechanisms.

The EventTarget interface is a standard event handling mechanism provided by browsers. It defines a set of methods for adding, removing, and triggering event listeners on nodes in the DOM tree. Almost all DOM elements implement the EventTarget interface, including the document object (Document), element objects (Element), document fragment objects (DocumentFragment), etc. Within the DOM standard, there are three main methods:

• addEventListener(type, listener[, options]): Adds an event listener to the event target.
• removeEventListener(type, listener[, options]): Removes an event listener from the event target.
• dispatchEvent(event): Manually triggers an event of the specified type.

Sometimes, when you delve into the browser's event loop, you might wonder about the relationship between the EventTarget, which follows the observer pattern, and the task queue of the event loop. The answer is simple: when an event is triggered on an EventTarget, all callback functions for that event are pushed into the macro task queue, awaiting execution.

Let's elaborate on the detailed process:

1. Registration of Event Listeners:

   • Event listeners are added to DOM elements either through the addEventListener method or through helper methods provided by browsers for simplification, such as onClick.

2. Event Triggering:

   • When a specific event occurs in the browser (e.g., click event, keyboard event, etc.), the browser first determines the affected element.
   • The browser creates an event object based on the event type and target element and sets the corresponding properties (e.g., type, target, etc.).

3. Event Propagation:

   • Event propagation consists of three phases: capturing phase, target phase, and bubbling phase.
   • In the capturing phase, the event propagates from the document root to the target element, traversing parent elements until reaching the target.
   • In the target phase, the event reaches the target element and triggers the event handlers.
   • In the bubbling phase, the event propagates from the target element back to the document root, traversing parent elements.

4. Event Handling:

   • During event propagation, the browser checks each traversed element for event listeners of the corresponding type. It's worth noting that a DOM object can have event listeners for both capturing and bubbling phases, and by default, listeners added via addEventListener are for the bubbling phase.
   • If an event listener is found, the browser calls the registered event handler and passes the corresponding event object as a parameter.
   • These event handlers can access properties of the event object. It's generally recommended to use event.currentTarget to obtain more information about the event and execute the appropriate logic.

5. Event Loop:

   • When an event is triggered, the registered listeners are added to the macro task queue.
   • When the execution stack is empty and there are no pending microtasks, the event loop dequeues a task from the macro task queue for execution. Thus, if a click action is bound to multiple listeners, it may execute across multiple ticks.

In summary, EventTarget is an interface for adding event listeners to DOM elements. Its relationship with the browser event loop lies in the fact that registered event listeners are ultimately added to the task queue of the event loop and executed at specific times.

Unlike native events, which are triggered asynchronously by the browser through the event loop, synthetic events (including dispatchEvent() and element.click() in modern browsers) execute event handlers synchronously. When these methods are called, all registered listeners run immediately in the current call stack, and the execution flow pauses until all handlers complete.

You can verify this with the following HTML code:

<!DOCTYPE html>
<html lang="en">
  <head>
    <

EventEmitter is a commonly used event-driven programming mechanism in Node.js, implementing custom event management through the observer pattern. Although EventEmitter is provided by Node.js, it can also be used in browsers through libraries like eventemitter3. Its main functionalities include:

• Registering event listeners: Adding event listeners through methods like on() or addListener().
• Triggering events: Emitting events using the emit() method and executing corresponding listeners.
• Removing event listeners: Removing specific event listeners through methods like off() or removeListener().

EventEmitter provides a flexible and powerful event handling mechanism, allowing developers to conveniently manage and handle events.

Below is how you can use EventEmitter natively in Node.js:

import events from 'events';

const eventEmitter = new events.EventEmitter();

However, if you want to use an EventEmitter-like mechanism in the frontend, such as implementing an event bus for scenarios where updates in one component require simultaneous responses from other distant components, traditional methods like React's event propagation or global variables might not be suitable. Therefore, you would either need to implement your own event bus or use third-party libraries.

Let's attempt to implement an EventEmitter ourselves and understand its underlying principles. Once we grasp the concept, we'll be better equipped to utilize it in the future.

class EventEmitter {
  constructor() 

Above is a brief implementation. Now, let's see how we can use it:

// Create a new EventEmitter instance
const emitter = new EventEmitter();

// Add an event listener
emitter.on('greet', (

That's it! We've successfully implemented an EventEmitter and demonstrated its simple usage.

Although both EventTarget and EventEmitter follow the observer pattern, their execution timing has a fundamental difference:

• EventTarget (Browser): Event callbacks are pushed into the macro task queue and executed asynchronously (e.g., a click event callback does not trigger immediately but waits for the current call stack to clear).
• EventEmitter (Node.js): Event callbacks are executed synchronously (when emit() is called, all listeners are executed immediately in the order they were registered).

This difference stems from their respective use cases:

• Browsers need to ensure UI event responsiveness and rendering performance (asynchronous execution avoids blocking).
• Node.js prioritizes low-latency handling of I/O events (synchronous execution is more efficient).

If you need to simulate asynchronous behavior with EventEmitter, you can manually wrap the callback:

emitter.on("asyncEvent", () => {
  setImmediate(() => console.log("Async Event"));

EventTarget and EventEmitter are both m...