Custom Errors and Error Codes

Learning Objectives

After completing this lesson, you will be able to:

• Explain Custom Errors and Error Codes using subclassed errors with code.
• Apply it to COURSE_NOT_FOUND without confusing Node.js with Express or TypeScript.
• Recognize and correct this failure mode: parsing English messages in clients.
• Decide when Custom Errors and Error Codes is the right tool: switch on codes.
• Describe the event-loop and I/O implications of this topic.
• Explain Custom Errors and Error Codes in terms of the Node.js runtime, not as a JavaScript language feature.
• Describe what V8, libuv, and the operating system each contribute.
• Identify whether the work is I/O-bound or CPU-bound.
• Handle operational errors without hiding programmer defects.
• Keep Express, TypeScript, and Node.js responsibilities distinct.
• Validate untrusted input at runtime before it reaches domain logic.
• Reason about event-loop delay, memory, and backpressure.
• Apply Custom Errors and Error Codes to a TechLearningPro backend use case.
• State when not to use this technique.
• Defend the design in an interview with trade-offs.

Introduction

A TechLearningPro backend must support COURSE_NOT_FOUND. Treating Node.js as "just JavaScript on a server" hides runtime, I/O, and security costs. The team needs a design that is explicit about subclassed errors with code and honest about what the process can and cannot do.

Node.js is a JavaScript runtime, not a programming language. This lesson treats Custom Errors and Error Codes as an engineering decision: what the runtime does, how the event loop is involved, and how the idea appears in a production TechLearningPro backend.

What Is This Concept?

In simple language: Codes are the contract; messages can change.

Professional explanation: Custom Errors and Error Codes is a Node.js runtime concern based on subclassed errors with code. It helps engineers implement COURSE_NOT_FOUND while remaining clear that Node.js executes JavaScript through V8 and reaches the operating system through libuv and Node.js APIs.

Why Do We Need It?

Without Custom Errors and Error Codes
        │
        ▼
Unclear runtime behavior or a fragile backend
        │
        ▼
Node.js solution
        │
        ▼
Predictable I/O, clearer ownership, safer operations

• It makes COURSE_NOT_FOUND an explicit backend responsibility.
• It prevents mixing browser JavaScript assumptions with server I/O.
• It gives reviewers a vocabulary for event-loop and failure behavior.
• It supports the key decision: switch on codes.
• It keeps framework and language features from being mistaken for the runtime.

Real-World Analogy

SKU numbers, not poem titles.

How It Works Internally

Runtime behavior

At runtime, Custom Errors and Error Codes follows ordinary JavaScript semantics inside V8, plus any Node.js or operating-system APIs involved in subclassed errors with code. Types and comments do not execute.

Event loop implications

If Custom Errors and Error Codes performs I/O, libuv schedules the work and the callback or Promise continuation later returns to the event loop. If it performs heavy CPU work on the main thread, timers, I/O callbacks, and incoming HTTP work wait.

1. 1. Name the invariant: COURSE_NOT_FOUND.
2. 2. Identify the Node.js mechanism: subclassed errors with code.
3. 3. Separate main-thread JavaScript from libuv / OS work.
4. 4. Define success, timeout, and failure paths.
5. 5. Validate untrusted input before domain logic.
6. 6. Add observability (logs, metrics, or traces) at the boundary.

Architecture

JavaScript
   │
   ▼
V8 (execute Custom Errors and Error Codes)
   │
   ▼
Node.js APIs / libuv
   │
   ▼
Operating system / thread pool
   │
   ▼
Callback / microtask queues
   │
   ▼
Event loop resumes the application
   │
   ▼
TechLearningPro response or side effect

Code Examples

// Custom Errors and Error Codes — smallest useful Node.js example
import { createRequire } from "node:module";

console.log("runtime", process.release.name);
console.log("pid", process.pid);

// Custom Errors and Error Codes — TechLearningPro service sketch
export async function handlecustomerrorsandcodes(input) {
  if (input == null || typeof input !== "object") {
    throw new Error("Untrusted input must be validated first");
  }
  return { ok: true, topic: "Custom Errors and Error Codes" };
}

// Custom Errors and Error Codes — production-oriented composition
export function createcustomerrorsandcodesHandler({ clock, logger }) {
  return async function handler(request) {
    const started = clock.now();
    try {
      return { status: 200, body: { topic: "Custom Errors and Error Codes" } };
    } finally {
      logger.info({ ms: clock.now() - started, topic: "custom-errors-and-codes" });
    }
  };
}

Enterprise Example

TechLearningPro uses Custom Errors and Error Codes while implementing COURSE_NOT_FOUND. The HTTP adapter stays thin, the application service owns the use case, and I/O is isolated. Reviewers can tell Node.js runtime behavior from Express helpers and from TypeScript types.

Student
   │
   ▼
API Gateway
   │
   ▼
Node.js service
   ├── Router / HTTP adapter
   ├── Authn / Authz
   ├── Application service
   └── Repository / client
            │
            ▼
     Database / Queue / Cache

Deep Dive

subclassed errors with code matters because it determines whether work is scheduled, blocked, or offloaded.

The principal design risk is parsing English messages in clients. A strong design keeps the event loop free, timeouts explicit, and diagnostics readable.

Custom Errors and Error Codes ends at a trust boundary. HTTP bodies, files, environment variables, and messages start untrusted.

The governing trade-off is switch on codes. Prefer the least infrastructure that solves a measured problem.

Common Mistakes

For each mistake, name the false assumption and replace it with an explicit runtime contract:

1. 1. Treating Custom Errors and Error Codes as a JavaScript language feature instead of a Node.js runtime concern.
2. 2. Assuming Node.js is secure by default.
3. 3. Ignoring the central pitfall: parsing English messages in clients.
4. 4. Blocking the event loop with CPU-heavy or synchronous I/O work.
5. 5. Presenting Express middleware as a Node.js core API.
6. 6. Trusting TypeScript types as runtime validation.
7. 7. Swallowing Promise rejections or using empty catch blocks.
8. 8. Adding clustering or worker threads before measuring the bottleneck.
9. 9. Logging secrets, tokens, or raw request bodies.
10. 10. Repeating an earlier lesson instead of composing the next layer.

Best Practices

• Keep the main thread free of unnecessary CPU work.
• Prefer async I/O over synchronous fs and crypto in request paths.
• Validate every external payload at the boundary.
• Use structured errors with request or correlation IDs.
• Load configuration from the environment, not hardcoded secrets.
• Separate Node.js platform setup from application services.
• Distinguish operational errors from programmer errors.
• Add timeouts to outbound HTTP, database, and queue calls.
• Treat Express as optional infrastructure, not the domain model.
• Use TypeScript for contracts; use runtime validators for input.
• Watch event-loop delay and memory in production.
• Keep dependencies minimal and audited.
• Make background jobs idempotent.
• Shut down HTTP servers and open handles on SIGTERM.
• Document when not to use the technique.
• Revisit the decision: switch on codes.

Performance

Node.js performance work starts with the event loop. Blocking the main thread delays every concurrent request. Measure before introducing clustering, worker threads, or extra infrastructure.

• Custom Errors and Error Codes is only as fast as the slowest I/O or CPU step on the path.
• Profile event-loop delay before blaming Node.js itself.
• Streams and backpressure matter when payloads are large.
• Do not enable cluster or worker_threads as a default recipe.

Security

Node.js is not secure by default. Security depends on application architecture, dependencies, configuration, validation, authentication, authorization, and deployment.

• Validate and authorize independently of UI or framework checks.
• Never execute unsanitized paths, commands, or query fragments.
• Store secrets in the environment or a secret manager.
• Keep dependency and supply-chain reviews part of delivery.
• Use Custom Errors and Error Codes to improve operations, not as a substitute for policy.

Real-World Architecture

Place Custom Errors and Error Codes in the narrowest layer that owns its invariant. HTTP adapters translate protocol; services coordinate use cases; repositories talk to data stores; the composition root wires Node.js process concerns.

Interview Questions & Answers

Practical Exercise

Problem: Add three domain error codes.

Difficulty: Intermediate

Requirements

• Use async I/O on the request path unless the lesson is about a blocking primitive.
• Validate untrusted input.
• Show a timeout or failure path.
• Do not treat Express or TypeScript as Node.js itself.

Expected behavior: A small TechLearningPro module that uses Custom Errors and Error Codes to support COURSE_NOT_FOUND and documents the runtime boundary.

Hints

• Start from subclassed errors with code.
• Watch for parsing English messages in clients.
• Ask whether the work belongs on the event loop or off it.

The full solution is intentionally withheld. Implement the contract, then review failure modes aloud.

Key Takeaways

• Custom Errors and Error Codes models COURSE_NOT_FOUND through subclassed errors with code.
• Node.js is a runtime; JavaScript is the language.
• V8 executes code; libuv and the OS perform most I/O.
• The main hazard is parsing English messages in clients.
• The key trade-off is switch on codes.
• Express and TypeScript are not Node.js.
• Types do not validate runtime input.
• Do not block the event loop without a measured reason.
• Security is an application and operations property.
• Compose the next lesson instead of reteaching this contract.

Summary

Custom Errors and Error Codes gives TechLearningPro a precise way to implement COURSE_NOT_FOUND through subclassed errors with code. Used with honest event-loop reasoning, boundary validation, and clear ownership, it improves backend change safety without pretending Node.js is a language or a security product.

Next Lesson Preview

Next, study Global and Express Error Handling. The next lesson extends this Node.js foundation with the next production concern.