Why the event system matters in Node.js - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the EventEmitter class from the 'events' module.

Node.js

const [1] = require('events');

Drag options to blanks, or click blank then click option'

AEventEmitter

BEmitter

CEvent

DEmitterClass

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong class name like 'Emitter' or 'Event'.

Forgetting to import the class before using it.

The EventEmitter class is the core of Node.js event system. Importing it correctly allows you to create event-driven code.

2fill in blank

medium

Complete the code to create a new instance of EventEmitter.

Node.js

const emitter = new [1]();

Drag options to blanks, or click blank then click option'

AEventEmitter

BEmitter

CEvent

DEmitterClass

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to instantiate a wrong or undefined class.

Using lowercase or misspelled class names.

You create a new event emitter by calling new EventEmitter(). This instance can then emit and listen to events.

3fill in blank

hard

Fix the error in the code to listen for the 'message' event.

Node.js

emitter.[1]('message', () => {
  console.log('Message received');
});

Drag options to blanks, or click blank then click option'

Alisten

BaddListenerEvent

ConMessage

Don

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like 'listen' or 'onMessage'.

Confusing event registration with event emitting.

The correct method to listen for events in Node.js EventEmitter is on. It registers a callback for the named event.

4fill in blank

hard

Fill both blanks to emit a 'data' event with a payload.

Node.js

emitter.[1]('[2]', { id: 1, value: 'hello' });

Drag options to blanks, or click blank then click option'

Aemit

Bdata

Csend

Dmessage

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'send' instead of 'emit' to trigger events.

Using wrong event names that don't match listeners.

To send an event, use emit with the event name and data. Here, the event name is 'data'.

5fill in blank

hard

Fill all three blanks to create a listener for 'update' event that logs the payload's status.

Node.js

emitter.[1]('[2]', (payload) => {
  console.log('Status:', payload.[3]);
});

Drag options to blanks, or click blank then click option'

Aon

Bupdate

Cstatus

Demit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'emit' instead of 'on' to listen for events.

Using wrong event names or property names.

Use on to listen for the 'update' event. The callback receives a payload object, and we access its 'status' property.

Practice

1. Why is the event system important in Node.js?

easy

A. It makes the program run slower by waiting for events.

B. It forces the program to run tasks one after another only.

C. It allows the program to respond to actions without stopping everything else.

D. It removes the need for any functions in the code.

Solution

1. Step 1: Understand event-driven programming

   Node.js uses events to react to actions like clicks or data arrival without pausing other tasks.

2. Step 2: Recognize the benefit of non-blocking behavior

   This means the program can do many things at once smoothly, improving performance.

3. Final Answer:

   It allows the program to respond to actions without stopping everything else. -> Option C

4. Quick Check:

   Event system = non-blocking response [OK]

Hint: Events let Node.js handle many tasks at once [OK]

Common Mistakes:

• Thinking events slow down the program
• Believing events force tasks to run one by one
• Assuming events remove the need for functions

2. Which of the following is the correct way to listen for an event named data on an EventEmitter instance emitter?

easy

A. emitter.on('data', () => { console.log('Data received'); });

B. emitter.listen('data', () => { console.log('Data received'); });

C. emitter.addEvent('data', () => { console.log('Data received'); });

D. emitter.catch('data', () => { console.log('Data received'); });

Solution

1. Step 1: Recall EventEmitter method names

   The correct method to listen for events is on, not listen, addEvent, or catch.

2. Step 2: Verify syntax correctness

   The syntax emitter.on('data', callback) is standard and valid in Node.js.

3. Final Answer:

   emitter.on('data', () => { console.log('Data received'); }); -> Option A

4. Quick Check:

   Use on to listen for events [OK]

Hint: Remember: EventEmitter uses .on() to listen [OK]

Common Mistakes:

• Using .listen() instead of .on()
• Using .addEvent() which doesn't exist
• Using .catch() which is for promises

3. What will the following Node.js code output?

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

emitter.on('greet', () => {
  console.log('Hello!');
});

emitter.emit('greet');
emitter.emit('greet');

medium

A. Hello! Hello!

B. Hello!

C. No output

D. Error: Event not found

Solution

1. Step 1: Understand event registration

   The code registers a listener for the 'greet' event that logs 'Hello!'.

2. Step 2: Analyze event emission

   The event 'greet' is emitted twice, so the listener runs twice, printing 'Hello!' two times.

3. Final Answer:

   Hello! Hello! -> Option A

4. Quick Check:

   Each emit triggers listener once [OK]

Hint: Each emit calls the listener once [OK]

Common Mistakes:

• Thinking emit only triggers once total
• Expecting no output without callback arguments
• Assuming error if event not predefined

4. Identify the error in this Node.js event code:

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

emitter.on('update', function() {
  console.log('Update received');
});

emitter.emit('updates');

medium

A. The listener function is missing parentheses.

B. The event name in emit does not match the listener's event name.

C. EventEmitter cannot be used without extending a class.

D. emit should be called before on to register listener.

Solution

1. Step 1: Compare event names in on and emit

   The listener listens for 'update' but emit triggers 'updates' (extra 's').

2. Step 2: Understand event matching

   Events must match exactly for the listener to run; here they differ, so no output occurs.

3. Final Answer:

   The event name in emit does not match the listener's event name. -> Option B

4. Quick Check:

   Event names must match exactly [OK]

Hint: Check event names match exactly [OK]

Common Mistakes:

• Assuming emit triggers all listeners regardless of name
• Thinking listener syntax is wrong without parentheses
• Believing emit order matters before on

5. You want to create a Node.js program that listens for a message event and counts how many times it happens. Which approach best uses the event system to keep the count updated and print it after 3 messages?

hard

A. Create three separate listeners for the message event, each printing the count.

B. Call emit('message') three times in a row without any listener.

C. Use a global variable outside the listener and reset it to zero every time the event fires.

D. Use an event listener that increments a counter each time message fires, then check the count inside the listener to print after 3.

Solution

1. Step 1: Use a counter inside the event listener

   Increment a variable each time the 'message' event fires to track occurrences.

2. Step 2: Check the count inside the listener

   When the count reaches 3, print the message count. This keeps logic together and reactive.

3. Final Answer:

   Use an event listener that increments a counter each time message fires, then check the count inside the listener to print after 3. -> Option D

4. Quick Check:

   Count inside listener for event-driven updates [OK]

Hint: Count events inside listener, print when count hits target [OK]

Common Mistakes:

• Emitting events without listeners
• Resetting counter on every event
• Using multiple listeners causing duplicate counts