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

leadme

v2.1.9

Published

Express middleware for logging to external service

Readme

LeadMe - Logger Middleware

Overview

Leadme is a middleware function for logging request and response data in a Node.js application. It allows configurable logging based on route paths or regular expressions.

Features

Important: All successful events will be logged in the LeadMe application.

  • Supports route-based and regex-based logging configuration.
  • Logs request and response data.
  • Allows filtering specific fields for logging.
  • Debug mode for additional insights.
  • All successful events will be logged in the LeadMe application.

Installation

npm i leadme

Usage

Import and Initialize

import express from "express";
import apiv1 from "./apiv1";
import { Leadme } from "leadme";

const app = express();

const leadme = new Leadme({ secretKey: "your-secret-key" });

app.use(leadme.middleware());

app.use("/api/v1", apiv1);

app.listen(3000, () => console.log("Server running on port 3000"));

Send custom event

import leadme from "../middlewares/logger-middleware";

try {
  const eventDetails = {
    type: "SIGN_IN", // Event type
    email: "[email protected]", // Email to associate the event with a user (optional)
    ip: "127.0.0.1", // IP address to identify the user (optional)
    data: {
      test: "TEST", // Additional data to log with the event (Any JSON data will suffice)
    },
  };

  await leadme.event(eventDetails);
} catch (err) {
  console.log(err, "ERROR WARNING");
}

Configuration Options

leadme({ logConfig, secretKey, sessionEmailField, debug })

| Parameter | Type | Default | Description | | ------------------- | ------- | ------------ | ------------------------------------------------------------------------------------------------------------------- | | logConfig | Object | null | Configuration for logging, supporting route paths and regex patterns. If not provided all routes will be logged in. | | secretKey | String | Required | Secret key for logging service. Obtained in leadme offer. | | sessionEmailField | String | user.email | Defines the session field for the user's email. | | debug | Boolean | false | Enables debug mode with additional logs. |

Example logConfig

{
  "/api/v1": { "req": true },
  "^/secure": { "req": ["email"] }
}
  • req: true logs the entire request.
  • req: ["email"] logs only the email field from the request.

Error Handling

  • If secretKey is missing, logging is disabled.

  • If logConfig is invalid, logging is disabled.