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 🙏

© 2024 – Pkg Stats / Ryan Hefner

echortech-logging

v1.3.6

Published

logging

Downloads

188

Readme

echortech-logging

A robust logging middleware for Express.js applications that provides structured logging with correlation IDs, trace IDs, and standardized log formats.

Installation

npm install echortech-logging

Features

  • Structured logging for Express.js applications
  • Support for info, warn, and error log levels
  • Automatic correlation ID and trace ID tracking
  • Request timing and response metrics
  • Custom tagging support

Usage

const express = require('express');
const echorLogger = require('echortech-logging'); 

const app = express();
const PORT = process.env.PORT || 3000;

// Middleware to simulate request info
app.use((req, res, next) => {
  req.info = { received: Date.now() };
  req.auth = { credentials: { sub: 'user123' } };
  req.correlationId = 'correlation-id-123';
  req.traceId = 'trace-id-123';
  next();
});

// Success route
app.get('/success', (req, res) => {
  const data = {
    statusCode: 200,
    message: 'This is a success message',
    responseTime: 123,
    result: { key: 'value' }
  };
  echorLogger.info(req, ['SUCCESS_TAG'], data);
  res.status(200).send('Success logged');
});

// Warning route
app.get('/warn', (req, res) => {
  const data = {
    statusCode: 200,
    message: 'This is a warning message',
    responseTime: 150,
    result: { key: 'value' }
  };
  echorLogger.warn(req, ['WARN_TAG'], data);
  res.status(200).send('Warning logged');
});

// Error route
app.get('/error', (req, res) => {
  const error = new Error('This is an error message');
  const data = {
    statusCode: 500,
    error: error.message,
    message: 'An error occurred',
    responseTime: 200
  };
  echorLogger.error(req, ['ERROR_TAG'], data, error);
  res.status(500).send('Error logged');
});

app.listen(PORT, () => {
  console.log(`Server is running on port ${PORT}`);
});

API Reference

echorLogger.info(req, tags, data)

Logs information level messages.

echorLogger.warn(req, tags, data)

Logs warning level messages.

echorLogger.error(req, tags, data, error)

Logs error level messages with error stack traces.

Parameters

  • req: Express request object containing:
    • info.received: Request receipt timestamp
    • auth.credentials.sub: User identifier
    • correlationId: Request correlation ID
    • traceId: Request trace ID
  • tags: Array of string tags for log categorization
  • data: Object containing log data
  • error: (Optional) Error object for error logging

Example Data Structure

{
  statusCode: 200,
  message: 'Log message',
  responseTime: 123,
  result: { key: 'value' }
}