Error-first callback convention in Node.js - Mini Project: Build & Apply

Error-first callback convention in Node.js

📖 Scenario: You are building a simple Node.js module that reads user data from a pretend database. You want to follow the common Node.js pattern called the error-first callback convention. This means your functions will pass an error as the first argument to the callback if something goes wrong, or null if everything is fine.

🎯 Goal: Create a function called getUserData that takes a userId and a callback. The function should simulate fetching user data. If the userId is not found, call the callback with an error as the first argument. If found, call the callback with null as the error and the user data as the second argument.

📋 What You'll Learn

Create an object called users with exactly these entries: 1: {name: 'Alice', age: 25}, 2: {name: 'Bob', age: 30}, 3: {name: 'Charlie', age: 35}

Create a variable called notFoundError that holds a new Error with the message 'User not found'

Write a function called getUserData that takes userId and callback parameters

Inside getUserData, check if userId exists in users. If not, call callback(notFoundError). If yes, call callback(null, userData) with the user data

Export the getUserData function using module.exports

💡 Why This Matters

🌍 Real World

Many Node.js modules and libraries use the error-first callback pattern to handle asynchronous operations and errors clearly.

💼 Career

Understanding this pattern is essential for working with legacy Node.js code and many popular libraries that have not yet adopted promises or async/await.

1

Create the users data object

Create an object called users with these exact entries: 1: {name: 'Alice', age: 25}, 2: {name: 'Bob', age: 30}, 3: {name: 'Charlie', age: 35}

Node.js

# Create the users object with 3 users
# Your code here

Hint

Use const users = {} and add the exact user entries inside.

2

Create the error variable

Create a variable called notFoundError that holds a new Error with the message 'User not found'

Node.js

const users = {
  1: {name: 'Alice', age: 25},
  2: {name: 'Bob', age: 30},
  3: {name: 'Charlie', age: 35}
};

// Create the notFoundError variable
# Your code here

Hint

Use new Error('User not found') to create the error.

3

Write the getUserData function

Write a function called getUserData that takes userId and callback parameters. Inside, check if userId exists in users. If not, call callback(notFoundError). If yes, call callback(null, userData) with the user data.

Node.js

const users = {
  1: {name: 'Alice', age: 25},
  2: {name: 'Bob', age: 30},
  3: {name: 'Charlie', age: 35}
};

const notFoundError = new Error('User not found');

// Write the getUserData function
# Your code here

Hint

Use if (!users[userId]) to check if user exists. Call callback accordingly.

4

Export the getUserData function

Export the getUserData function using module.exports.

Node.js

const users = {
  1: {name: 'Alice', age: 25},
  2: {name: 'Bob', age: 30},
  3: {name: 'Charlie', age: 35}
};

const notFoundError = new Error('User not found');

function getUserData(userId, callback) {
  if (!users[userId]) {
    callback(notFoundError);
  } else {
    callback(null, users[userId]);
  }
}

// Export getUserData
# Your code here

Hint

Use module.exports = getUserData; to export the function.

Practice

1. What is the main purpose of the error-first callback convention in Node.js?

easy

A. To avoid using callbacks and use promises instead

B. To pass the result as the first argument and error as the second

C. To handle errors only after all callbacks have finished

D. To always pass the error as the first argument to the callback function

Solution

1. Step 1: Understand the callback argument order

   The error-first callback convention means the first argument is always the error if any occurred.

2. Step 2: Recognize the purpose of this order

   This helps developers check for errors before processing results, making code safer and clearer.

3. Final Answer:

   To always pass the error as the first argument to the callback function -> Option D

4. Quick Check:

   Error is first argument [OK]

Hint: Error always comes first in callbacks [OK]

Common Mistakes:

• Thinking result comes before error
• Confusing error-first with promise usage
• Ignoring error handling in callbacks

2. Which of the following is the correct syntax for an error-first callback function in Node.js?

easy

A. function callback(error, result) { ... }

B. function callback(result, error) { ... }

C. function callback() { ... }

D. function callback(result) { ... }

Solution

1. Step 1: Identify the correct parameter order

   The error-first callback convention requires the first parameter to be error, second to be result.

2. Step 2: Match the syntax

   Only the function with parameters (error, result) follows this convention correctly.

3. Final Answer:

   function callback(error, result) { ... } -> Option A

4. Quick Check:

   Callback params: error first, result second [OK]

Hint: Error is first parameter in callback functions [OK]

Common Mistakes:

• Swapping error and result parameters
• Omitting error parameter
• Using only one parameter for result

3. Consider the following code snippet:

function readFile(callback) {
  setTimeout(() => {
    callback(null, 'file content');
  }, 100);
}

readFile((err, data) => {
  if (err) {
    console.log('Error:', err);
  } else {
    console.log('Data:', data);
  }
});

What will be printed to the console?

medium

A. Error: null

B. Data: file content

C. Error: file content

D. Nothing will be printed

Solution

1. Step 1: Analyze the callback invocation

   The callback is called with null as error and 'file content' as data after 100ms.

2. Step 2: Check the callback logic

   Since err is null (no error), the else branch runs and logs 'Data: file content'.

3. Final Answer:

   Data: file content -> Option B

4. Quick Check:

   Null error means success, so data logs [OK]

Hint: Null error means no error, print data [OK]

Common Mistakes:

• Printing error when error is null
• Confusing error and data values
• Expecting no output due to async

4. Identify the error in this code using error-first callback convention:

function getData(callback) {
  const error = null;
  const result = 'Success';
  callback(result, error);
}

getData((err, data) => {
  if (err) {
    console.log('Error:', err);
  } else {
    console.log('Data:', data);
  }
});

medium

A. No error handling is needed here

B. The callback function is missing

C. The callback arguments are reversed; error should be first

D. The error variable should be a string, not null

Solution

1. Step 1: Check callback argument order

   The callback is called with (result, error) but error-first convention requires (error, result).

2. Step 2: Understand impact of reversed arguments

   This reversal causes the callback to treat 'Success' as error and null as data, breaking logic.

3. Final Answer:

   The callback arguments are reversed; error should be first -> Option C

4. Quick Check:

   Callback args must be (error, result) [OK]

Hint: Error must be first argument in callback calls [OK]

Common Mistakes:

• Passing result before error
• Ignoring argument order in callbacks
• Assuming error can be second argument

5. You have a function that reads user data asynchronously and uses an error-first callback:

function fetchUser(id, callback) {
  if (id <= 0) {
    callback(new Error('Invalid ID'), null);
  } else {
    setTimeout(() => {
      callback(null, { id, name: 'Alice' });
    }, 50);
  }
}

How should you call fetchUser to correctly handle errors and print the user's name or the error message?

hard

A. fetchUser(1, (err, user) => { if (err) console.log(err.message); else console.log(user.name); });

B. fetchUser(1, (err, user) => { if (user) console.log(user.name); else console.log(err.message); });

C. fetchUser(1, (user, err) => { if (err) console.log(err.message); else console.log(user.name); });

D. fetchUser(1, (err, user) => { console.log(user.name); });

Solution

1. Step 1: Check callback parameter order and error handling

   The callback parameters must be (err, user). We check if err exists first to handle errors.

2. Step 2: Verify correct conditional logic

   If err exists, print err.message; otherwise, print user.name. fetchUser(1, (err, user) => { if (err) console.log(err.message); else console.log(user.name); }); follows this correctly.

3. Final Answer:

   fetchUser(1, (err, user) => { if (err) console.log(err.message); else console.log(user.name); }); -> Option A

4. Quick Check:

   Check error first, then use user [OK]

Hint: Always check error before using result in callback [OK]

Common Mistakes:

• Swapping error and user parameters
• Not checking error before accessing user
• Ignoring error handling completely