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

@satyajeetsahoo/logger

v2.1.3

Published

Small structured JSON logger for Node.js

Downloads

38

Readme

@satyajeetsahoo/logger

A unified contextual logging service designed for microservices and express applications.

Why use this package?

When debugging production APIs with thousands of concurrent requests, a simple console.log is useless because you don't know which request caused the log. This logger automatically injects traceId and contextual data into every log line, making tracing errors through systems like Datadog or ELK effortless.

Features

  • Contextual Logging: Automatically attaches Express request metadata.
  • Child Loggers: Create isolated loggers for specific modules.
  • Multiple Transports: Log to the console, files, Azure, or Cloudflare R2.

Installation

npm install @satyajeetsahoo/logger

Configuration & Express Setup

import express from 'express';
import { createLogger, requestContext, withLogContext } from '@satyajeetsahoo/logger';

const app = express();

// 1. Create the base logger
export const logger = createLogger({ service: 'employee-api', level: 'info' });

// 2. Add the context middleware to Express
app.use(requestContext()); 

// 3. Log anywhere!
app.get('/users/:id', (req, res) => {
  logger.info('Fetching user', { userId: req.params.id });
  // Output includes traceId, HTTP method, URL, and userId!
});

Advanced Usage

Child Loggers

Perfect for isolating logs within specific services or classes.

const paymentLogger = logger.child({ module: 'PaymentGateway' });

paymentLogger.info('Processing transaction');
// Includes { module: 'PaymentGateway' } automatically

Async Context

Wrap background jobs to inject context without passing the logger down deeply nested functions.

withLogContext({ jobId: 123 }, async () => {
  logger.info('Job started'); // Logs { jobId: 123 }
  await processPayment();     // Any logs inside here also get { jobId: 123 }
});