[Solved] You wrote this code to catch unhandled promise rejections:process.on('unhandledRejection', (error) => { console.log('Caught:', error); }); Promise.reject('Oops!');But the console shows Caught: Oops!... | Node.js

Node.js - Error Handling Patterns

You wrote this code to catch unhandled promise rejections:

process.on('unhandledRejection', (error) => {
  console.log('Caught:', error);
});

Promise.reject('Oops!');

But the console shows Caught: Oops! instead of an error message. What is the issue?

AThe handler function must be async to catch rejections

BThe event name should be 'unhandledRejections' (plural)

CYou must use try-catch instead of process.on for promises

DThe rejection reason is a string, not an Error object, so error.message is undefined

Step-by-Step Solution

Solution:

Step 1: Check the rejection reason type
The promise rejects with a string 'Oops!', not an Error object.
Step 2: Understand how the handler logs the error
The handler logs the whole error variable, which is the string 'Oops!', so it prints exactly that.
Final Answer:
The rejection reason is a string, not an Error object, so error.message is undefined -> Option D
Quick Check:
Rejection reason type affects error.message presence [OK]

Quick Trick: Rejection reason can be any type; strings have no .message [OK]

Common Mistakes:

Master "Error Handling Patterns" in Node.js

9 interactive learning modes - each teaches the same concept differently

More Node.js Quizzes

You wrote this code to catch unhandled promise rejections: