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

@mr-aftab-ahmad-khan/logmesh

v0.1.3

Published

AI-native structured logger with request tracing, error clustering, sampling, redaction, and pretty/JSON transports.

Downloads

239

Readme

logmesh

Structured logger built for the AI debugging era. Every record is JSON, every request gets a trace ID, every error gets a stable fingerprint you can group, alert on, and feed to an LLM.

Why

  • Pretty terminal output in dev, JSON in prod (auto-detected).
  • Built-in PII/secret redaction (password, token, cookie, authorization, …).
  • Async-context trace IDs that flow through every middleware, handler, and DB call.
  • Error fingerprinting + clustering so you can answer "how many users hit this exact bug today?"
  • Pluggable transports (JSON, pretty, file, memory) and sampling.

Install

npm install @mr-aftab-ahmad-khan/logmesh

Basics

import { createLogger } from "@mr-aftab-ahmad-khan/logmesh";

const log = createLogger({ level: "info", bindings: { app: "api" } });

log.info("server started", { port: 3000 });
log.warn({ retries: 3, endpoint: "/orders" }, "retrying upstream");

try {
  await doWork();
} catch (err) {
  log.error(err, { msg: "work failed", userId: "u_1" });
}

Express integration

import express from "express";
import { createLogger, expressLogger, getContext } from "@mr-aftab-ahmad-khan/logmesh";

const log = createLogger();
const app = express();

app.use(expressLogger({ logger: log }));

app.get("/me", (req, res) => {
  log.info("loading profile");           // automatically tagged with traceId
  res.json({ traceId: getContext()?.traceId });
});

Every log inside the request handler is automatically annotated with the request's trace ID via AsyncLocalStorage.

Error clustering

import { ErrorClusterer, memoryTransport, createLogger } from "@mr-aftab-ahmad-khan/logmesh";

const mem = memoryTransport();
const log = createLogger({ transports: [mem] });
const cluster = new ErrorClusterer();

log.error(new Error("DB timeout"));
log.error(new Error("DB timeout"));

for (const record of mem.records) cluster.observe(record);
console.log(cluster.summarize());
// [error] 5d3f… ×2  DB timeout (first=…, last=…)

Use it to drive an /errors endpoint, Slack alert, or LLM summarizer.

Transports

import {
  jsonTransport,
  prettyTransport,
  fileTransport,
  memoryTransport,
  createLogger,
} from "@mr-aftab-ahmad-khan/logmesh";

const log = createLogger({
  transports: [
    prettyTransport(),                    // dev terminal
    fileTransport("./logs/app.log"),      // newline-delimited JSON
  ],
});

Write your own by implementing Transport:

const datadogTransport = {
  name: "datadog",
  write(record) { sendToDatadog(record); },
};

Redaction

const log = createLogger({ redactKeys: ["x-user-token", "social_security"] });
log.info("req", { headers: { "x-user-token": "secret" } });
// -> "headers": { "x-user-token": "[REDACTED]" }

Defaults already redact password, pass, secret, token, apikey, authorization, cookie, set-cookie, session, ssn, creditcard, cvv.

Sampling

createLogger({
  sampler: (record) => record.level === "info" ? Math.random() < 0.1 : true,
});

API

| Function | Purpose | | --- | --- | | createLogger(options) | Construct a logger | | logger.child(bindings) | Inherit all options, append bindings | | logger.{trace,debug,info,warn,error,fatal}(msg \| obj \| err, ctx?) | Emit a record | | expressLogger({ logger }) | Express middleware with trace IDs | | runWithContext(ctx, fn) | Manually set async context | | ErrorClusterer | Group records by fingerprint | | serializeError(err) | Convert any thrown value to a JSON-safe shape | | errorFingerprint(serialized) | 12-char stable hash | | buildRedactor(extraKeys) | Reusable redactor function |

License

MIT