npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@wictlab/error-catch

v1.0.3

Published

Advanced Express logging middleware

Downloads

21

Readme

@wictlab/error-catch

npm version License: MIT

@wictlab/error-catch provides robust and customizable logging middleware for Express.js applications, designed to streamline the process of capturing request, response, and error logs, and dispatching them to a centralized logging API. This package helps developers monitor their applications effectively and debug issues with ease.

Features

  • Request/Response Logging: Automatically logs details for every incoming HTTP request and outgoing response.
  • Error Logging: Catches and logs errors that occur within your Express application, providing crucial debugging information.
  • Centralized Logging: Easily send all logs to a specified external logging API endpoint.
  • Service Identification: Tag logs with a serviceName to distinguish logs from different microservices or applications.
  • Customizable: Configure logging behavior to fit your application's needs.

Installation

Install the package using npm:

npm install @wictlab/error-catch

Usage

Integrate @wictlab/error-catch into your Express application to start logging.

Basic Setup

First, import the middleware functions:

const express = require('express');
const { loggerMiddleware, errorLoggerMiddleware } = require('@wictlab/error-catch');

const app = express();

// Enable JSON body parsing
app.use(express.json());

// Configure and use the request/response logger middleware
app.use(loggerMiddleware({
  logApiUrl: 'http://localhost:3000/log', // Your centralized logging API endpoint
  serviceName: 'my-express-app',         // A name to identify this service in your logs
}));

// Example route
app.get('/', (req, res) => {
  res.status(200).send('Hello World! Check your logs.');
});

// Example route that throws an error
app.get('/error', (req, res, next) => {
  next(new Error('This is a test error!'));
});

// Configure and use the error logger middleware
// IMPORTANT: This middleware should be placed AFTER all other routes and middleware
// to ensure it catches errors from them.
app.use(errorLoggerMiddleware({
  logApiUrl: 'http://localhost:3000/log', // Your centralized logging API endpoint
}));

const PORT = 3000;
app.listen(PORT, () => {
  console.log(`Server listening on port ${PORT}`);
});

loggerMiddleware(options)

This middleware logs details about incoming requests and outgoing responses.

Options:

  • logApiUrl (String, required): The URL of your centralized logging API endpoint where request/response logs will be sent.
  • serviceName (String, required): A unique identifier for your service, which will be included in the logs.

errorLoggerMiddleware(options)

This middleware catches and logs errors that occur within your Express application. It should always be the last middleware added to your Express app.

Options:

  • logApiUrl (String, required): The URL of your centralized logging API endpoint where error logs will be sent.
  • serviceName (String, optional): A unique identifier for your service. If not provided, it attempts to infer it from loggerMiddleware's configuration or defaults to 'unknown-service'. It's recommended to explicitly provide it for clarity.

Contributing

We welcome contributions! Please feel free to submit issues or pull requests.

License

This project is licensed under the MIT License - see the LICENSE file for details.