0Pricing
Node.js Backend Development Bootcamp · Pelajaran

Strategi Penanganan Galat Global

Terapkan mekanisme penanganan galat terpusat untuk mengelola pengecualian dengan baik dan memberikan respons galat yang konsisten.

Strategi Penanganan Galat Global adalah pelajaran Node.js Backend Development Bootcamp gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Node.js Backend Development Bootcamp, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Node.js Backend Development Bootcamp mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Centralized Errors in Express

When building an API, errors are inevitable. How you handle them can drastically affect user experience and application stability.

Scattered try...catch blocks in every route can become messy and inconsistent. This lesson introduces global error handling in Express.js.

Express's Default Error Response

By default, if an error occurs in an Express route or middleware and isn't caught, Express will:

  • Send a response with a 500 Internal Server Error status code.
  • Include the error's stack trace in the response.

This default behavior is not ideal for production, as it exposes sensitive server details to clients.

The Special Error Middleware

Express recognizes a special type of middleware for error handling. Unlike regular middleware which takes (req, res, next), error-handling middleware takes four arguments:

  • err: The error object passed by Express.
  • req: The request object.
  • res: The response object.
  • next: The next middleware function.

Express knows to skip all other middleware and send the error directly to this special handler.

Your First Error Middleware

Let's create a basic error handling middleware. This middleware should be placed after all other routes and middleware in your app.js file.

Try running this simple Express app:

const express = require('express');
const app = express();

// A route that intentionally throws an error
app.get('/error', (req, res, next) => {
  const err = new Error('Something went wrong!');
  err.statusCode = 400;
  next(err); // Pass the error to the error middleware
});

// Global Error Handling Middleware (must be last)
app.use((err, req, res, next) => {
  console.error(err.stack); // Log the error for debugging
  const statusCode = err.statusCode || 500;
  res.status(statusCode).json({
    status: 'error',
    message: err.message || 'An unexpected error occurred!'
  });
});

const PORT = 3000;
app.listen(PORT, () => {
  console.log(`Server running on port ${PORT}`);
  console.log('Visit http://localhost:3000/error to see error handling');
});

Operational vs. Programmatic Errors

It's crucial to distinguish between error types:

  • Operational Errors: Predictable errors from system operations (e.g., invalid user input, network issues, resource not found). These are 'soft' errors we can handle gracefully and send specific messages to the client.
  • Programmatic Errors: Bugs in your code (e.g., trying to read property of undefined, database connection failures). These are 'hard' errors that indicate a problem with your application logic and might require restarting the process.

Our global handler should treat these differently.

Crafting Custom Errors

To better categorize and handle errors, we can create custom error classes. This allows us to attach specific properties like statusCode and isOperational to our errors.

Here's a simple AppError class:

// utils/appError.js
class AppError extends Error {
  constructor(message, statusCode) {
    super(message);

    this.statusCode = statusCode;
    this.status = `${statusCode}`.startsWith('4') ? 'fail' : 'error';
    this.isOperational = true;

    Error.captureStackTrace(this, this.constructor);
  }
}

module.exports = AppError;

Using Custom Errors in Routes

Now that we have our AppError class, we can use it in our routes to throw specific, operational errors. When an AppError is thrown and caught by next(err), our global handler can provide a tailored response.

Run this example and try visiting /user/123 (valid) and /user/abc (invalid ID):

const express = require('express');
const AppError = require('./utils/appError'); // Assuming appError.js is in a 'utils' folder
const app = express();

// Example route using custom error
app.get('/user/:id', (req, res, next) => {
  const userId = parseInt(req.params.id);

  if (isNaN(userId)) {
    return next(new AppError('Invalid user ID provided!', 400));
  }

  res.status(200).json({
    status: 'success',
    data: { id: userId, name: `User ${userId}` }
  });
});

// Global Error Handling Middleware (must be last)
app.use((err, req, res, next) => {
  console.error(err.stack);

  const statusCode = err.statusCode || 500;
  const status = err.status || 'error';

  if (err.isOperational) {
    res.status(statusCode).json({
      status: status,
      message: err.message
    });
  } else {
    // For programmatic errors, send a generic message in production
    res.status(500).json({
      status: 'error',
      message: 'Something went very wrong!'
    });
  }
});

const PORT = 3000;
app.listen(PORT, () => {
  console.log(`Server running on port ${PORT}`);
  console.log('Visit http://localhost:3000/user/1 to see success');
  console.log('Visit http://localhost:3000/user/abc to see custom error');
});

// --- Create utils/appError.js with the content from the previous scene for this to run ---

Intelligent Error Responses

Our error handler can be further refined to provide different responses based on the environment (development vs. production).

  • Development: Send full error details (stack trace) for debugging.
  • Production: Send minimal, user-friendly messages for operational errors and generic messages for programmatic errors (to hide internal details).

This approach keeps your API secure and informative.

Catching the Unforeseen

Express middleware only catches errors that occur within the request-response cycle and are passed with next(err). What about errors outside of this?

  • Uncaught Exceptions: Synchronous errors that are not handled by any try...catch block.
  • Unhandled Rejections: Promise rejections that don't have a .catch() handler.

Node.js provides global process event listeners for these critical errors, which should ideally shut down the application after logging the error.

// In your server.js or app.js, before app.listen
process.on('uncaughtException', err => {
  console.error('UNCAUGHT EXCEPTION! Shutting down...');
  console.error(err.name, err.message, err.stack);
  process.exit(1); // Exit with failure code
});

// After app.listen, for unhandled promise rejections
process.on('unhandledRejection', err => {
  console.error('UNHANDLED REJECTION! Shutting down...');
  console.error(err.name, err.message);
  // Optionally close server first, then exit
  server.close(() => {
    process.exit(1);
  });
});

Error Handling Challenge

You've learned about Express error handling. Which of the following is the correct signature for an Express error handling middleware?

Global Error Handling Summary

Great job! You've learned how to implement robust error handling in your Express applications.

  • Express uses a special 4-argument middleware for error handling.
  • Distinguish between operational and programmatic errors.
  • Create custom error classes to add context to your errors.
  • Implement global listeners for uncaught exceptions and unhandled rejections.

Centralized error handling makes your API more reliable, secure, and easier to debug!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Strategi Penanganan Galat Global” gratis?

Ya — teks lengkap “Strategi Penanganan Galat Global” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Node.js Backend Development Bootcamp, upgrade ke CoddyKit PRO. Kursus Node.js Backend Development Bootcamp mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Strategi Penanganan Galat Global”?

Terapkan mekanisme penanganan galat terpusat untuk mengelola pengecualian dengan baik dan memberikan respons galat yang konsisten. Kamu berlatih Node.js Backend Development Bootcamp dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Node.js Backend Development Bootcamp?

Tidak diperlukan pengalaman sebelumnya. Node.js Backend Development Bootcamp di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Strategi Penanganan Galat Global” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Node.js Backend Development Bootcamp ini?

Ya. Setiap pelajaran Node.js Backend Development Bootcamp menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Mengembangkan Middleware Express Khusus
  2. Strategi Penanganan Galat Global
  3. Validasi Masukan dengan Joi/Express-Validator
  4. Middleware Autentikasi dengan JWT
← Kembali ke Node.js Backend Development Bootcamp