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

@stacklenzz/server

v1.0.0

Published

Stacklenzz Observability SDK for Express and NestJS with OpenTelemetry, Prometheus metrics, and Winston logging

Readme

It provides:

  • Zero-Config Telemetry Endpoint (/api/observability/stats) feeding real-time operations into frontend dashboards.
  • Built-in Error Intelligence:
    • Automatic 4xx & 5xx error capture with stack traces and request context (OS, Node version, memory, IP, user-agent, query params).
    • Deterministic fingerprinting to automatically group recurring issues and track occurrences.
    • Event breadcrumbs (addBreadcrumb, getBreadcrumbs) recording HTTP requests, DB queries, and logs leading up to an error.
  • Sliding Window Error Rates & Counters: Rolling time windows (last1m, last5m, last15m, last30m, last1h, last2h, last24h, last7d, last30d).
  • Prometheus Metrics: Standard Node.js runtime metrics (CPU, RSS, Heap, Event Loop lag) + HTTP request counters, histograms, and active request gauges via @prometheus-io/client on /metrics.
  • OpenTelemetry Distributed Tracing: Auto-instrumentations + OTLP trace exporter with Winston trace correlation (trace_id and span_id).
  • Clean Subpath Exports:
    • @stacklenzz/server (core)
    • @stacklenzz/server/express
    • @stacklenzz/server/nestjs

Installation

npm install @stacklenzz/server
# or
pnpm add @stacklenzz/server

Peer Dependencies:

  • Express: npm install express
  • NestJS: npm install @nestjs/common @nestjs/core @nestjs/platform-express rxjs reflect-metadata

Package Subpath Exports

@stacklenzz/server is organized into clean, modern subpath exports:

| Subpath | Purpose | Key Exports | |---|---|---| | @stacklenzz/server/express | Express.js framework integration | setupObservability, createObservabilityMiddleware, createMetricsHandler, createStatsHandler | | @stacklenzz/server/nestjs | NestJS framework integration | ObservabilityModule, ObservabilityInterceptor, ObservabilityExceptionFilter | | @stacklenzz/server/core | Core telemetry, metrics, Winston logger & snapshots | getObservabilitySnapshot, Counter, Gauge, register, logger, addBreadcrumb, trace, context, resetMetrics | | @stacklenzz/server | Default root export | Re-exports all core primitives + Express utilities |


Quick Start: Express (@stacklenzz/server/express)

Instrument your Express application with a single call:

import express from "express";
import { setupObservability } from "@stacklenzz/server/express";
import { logger, addBreadcrumb } from "@stacklenzz/server/core";

const app = express();

// Automatically attaches Prometheus /metrics, Winston logging, and /api/observability/stats
setupObservability(app, {
  serviceName: "my-express-api",
  environment: "production",
  statsPath: "/api/observability/stats", // default
  metricsPath: "/metrics",              // default
});

app.get("/api/users", (req, res) => {
  // Add breadcrumbs for key operations
  addBreadcrumb({ category: "auth", message: "User authenticated", level: "info" });
  res.json([{ id: 1, name: "Alice" }]);
});

// Fallback for non-existent routes (automatically tracked as 404 in dashboard)
app.use((req, res) => {
  res.status(404).json({ statusCode: 404, error: "Not Found", message: `Cannot ${req.method} ${req.url}` });
});

app.listen(5000, () => console.log("API running on port 5000"));

Quick Start: NestJS (@stacklenzz/server/nestjs)

Synchronous Setup:

In your root module (app.module.ts):

import { Module } from "@nestjs/common";
import { ObservabilityModule } from "@stacklenzz/server/nestjs";

@Module({
  imports: [
    ObservabilityModule.forRoot({
      serviceName: "my-nestjs-api",
      environment: "production",
      autoInitTracing: true,
    }),
  ],
})
export class AppModule {}

Asynchronous Setup with ConfigService:

import { Module } from "@nestjs/common";
import { ConfigModule, ConfigService } from "@nestjs/config";
import { ObservabilityModule } from "@stacklenzz/server/nestjs";

@Module({
  imports: [
    ConfigModule.forRoot(),
    ObservabilityModule.forRootAsync({
      imports: [ConfigModule],
      inject: [ConfigService],
      useFactory: (config: ConfigService) => ({
        serviceName: config.get<string>("APP_NAME", "my-nestjs-api"),
        environment: config.get<string>("NODE_ENV", "production"),
      }),
    }),
  ],
})
export class AppModule {}

In your main.ts, enable CORS so your frontend dashboard can read telemetry:

import { NestFactory } from "@nestjs/core";
import { AppModule } from "./app.module.js";

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  app.enableCors({ origin: "*" });
  await app.listen(5000);
}
bootstrap();

Note: ObservabilityModule.forRoot() automatically registers both ObservabilityInterceptor (for request metrics and timing) and ObservabilityExceptionFilter (for global 404, 4xx, and 5xx error captures).


Node.js Framework Compatibility (Fastify, Koa, Hono, Hapi, Pure Node)

@stacklenzz/server is framework-agnostic at its core. If you are using frameworks other than Express or NestJS, you can import @stacklenzz/server/core to wire up telemetry, error recording, and your snapshot endpoint:

1. Fastify Integration

import Fastify from "fastify";
import { getObservabilitySnapshot, recordError, addBreadcrumb, logger } from "@stacklenzz/server/core";

const fastify = Fastify({ logger: false });

// Expose telemetry snapshot endpoint for @stacklenzz/ui
fastify.get("/api/observability/stats", async (request, reply) => {
  const snapshot = await getObservabilitySnapshot();
  return reply.header("Access-Control-Allow-Origin", "*").send(snapshot);
});

// Fastify error handler capturing failure details into dashboard
fastify.setErrorHandler((error, request, reply) => {
  recordError({
    message: error.message,
    stack: error.stack,
    route: request.url,
    method: request.method,
    statusCode: error.statusCode || 500,
  });
  reply.status(error.statusCode || 500).send({ error: error.message });
});

2. Koa Integration

import Koa from "koa";
import Router from "@koa/router";
import { getObservabilitySnapshot, recordError } from "@stacklenzz/server/core";

const app = new Koa();
const router = new Router();

// Stats endpoint
router.get("/api/observability/stats", async (ctx) => {
  ctx.set("Access-Control-Allow-Origin", "*");
  ctx.body = await getObservabilitySnapshot();
});

// Error tracking middleware
app.use(async (ctx, next) => {
  try {
    await next();
  } catch (err: any) {
    recordError({
      message: err.message,
      stack: err.stack,
      route: ctx.path,
      method: ctx.method,
      statusCode: err.status || 500,
    });
    throw err;
  }
});

app.use(router.routes());

3. Hono (Node.js Adapter)

import { Hono } from "hono";
import { serve } from "@hono/node-server";
import { getObservabilitySnapshot, recordError } from "@stacklenzz/server/core";

const app = new Hono();

app.get("/api/observability/stats", async (c) => {
  c.header("Access-Control-Allow-Origin", "*");
  const snapshot = await getObservabilitySnapshot();
  return c.json(snapshot);
});

app.onError((err, c) => {
  recordError({
    message: err.message,
    stack: err.stack,
    route: c.req.path,
    method: c.req.method,
    statusCode: 500,
  });
  return c.text("Internal Server Error", 500);
});

serve(app, (info) => console.log(`Listening on http://localhost:${info.port}`));

Pluggable Database Crash Log Adaptor (crashLogAdaptor)

Persist 5xx server crashes directly to a database of your choice (PostgreSQL, MongoDB, Redis, Prisma, TypeORM, etc.) and manage them interactively inside the UI dashboard.

  • Opt-in Only: If omitted, standard in-memory ring buffers function with zero overhead.
  • 5xx / Crash Trigger Only: Fires only for 5xx HTTP responses or uncaught server crashes (4xx client errors and info logs are excluded).
  • Non-Blocking Fire-and-Forget: Executes asynchronously so database write latency or outages never slow down or crash client HTTP requests.
  • Full UI Deletion & Sync: Provide list, delete, and clearAll handlers to inspect, filter, delete individual logs, or purge all database crash logs directly from the UI.

Configuration via Express:

import express from "express";
import { setupObservability, CrashLogEntry } from "@stacklenzz/server";

const app = express();

setupObservability(app, {
  serviceName: "user-service",
  crashLogAdaptor: {
    // 1. Save 5xx crash log
    save: async (entry: CrashLogEntry) => {
      await prisma.crashLog.create({ data: entry });
    },
    // 2. Query logs for the UI
    list: async () => {
      return await prisma.crashLog.findMany({ orderBy: { timestamp: "desc" } });
    },
    // 3. Delete individual log from UI
    delete: async (id: string) => {
      await prisma.crashLog.delete({ where: { id } });
    },
    // 4. Clear all logs from UI
    clearAll: async () => {
      await prisma.crashLog.deleteMany({});
    },
  },
});

Configuration via NestJS:

import { Module } from "@nestjs/common";
import { ObservabilityModule } from "@stacklenzz/server/nestjs";

@Module({
  imports: [
    ObservabilityModule.forRoot({
      serviceName: "user-service",
      crashLogAdaptor: {
        save: async (entry) => {
          await db.crashLogs.insert(entry);
        },
      },
    }),
  ],
})
export class AppModule {}

Telemetry & Incident Intelligence Features

1. Adding Breadcrumbs

Trace operations leading up to unexpected errors:

import { addBreadcrumb } from "@stacklenzz/server";

addBreadcrumb({
  category: "db",
  message: "Query executed on users table",
  level: "info",
  data: { queryTimeMs: 4.2 },
});

2. Structured & Automatic Error Logging

Logs automatically correlate with active OpenTelemetry spans and are captured into the recent error stream if level is error.

Automatic Error Logging (logger.error(err)):

You do not need to manually pass route, method, status, or stack. Passing the Error instance directly extracts message and stack while request metadata is captured automatically:

import { logger } from "@stacklenzz/server";

try {
  throw new Error("Payment gateway connection reset");
} catch (err) {
  // Automatically captures error message and full stack trace!
  logger.error(err);
}

Manual Additional Context:

You can also pass custom metadata or response payloads:

logger.error("Payment authorization failed", {
  responseBody: { reason: "Gateway timeout" },
});

Advanced SDK Utilities

1. Programmatic Telemetry Snapshot (getObservabilitySnapshot)

Generate an operational JSON snapshot directly in your backend code without an HTTP request:

import { getObservabilitySnapshot } from "@stacklenzz/server";

const snapshot = await getObservabilitySnapshot();
console.log("Current Error Rate:", snapshot.summary.errorRate);
console.log("Top Endpoints:", snapshot.http.topEndpoints);

2. Custom Prometheus Metrics (Counter, Gauge, register)

Register custom business metrics directly on the /metrics endpoint:

import { Counter, register } from "@stacklenzz/server";

const ordersCounter = new Counter({
  name: "orders_processed_total",
  help: "Total processed checkout orders",
  registers: [register],
});

ordersCounter.inc();

3. OpenTelemetry API Re-exports (trace, context)

Access OpenTelemetry tracing primitives directly without installing @opentelemetry/api:

import { trace, context } from "@stacklenzz/server";

const activeSpan = trace.getSpan(context.active());
if (activeSpan) {
  console.log("Trace ID:", activeSpan.spanContext().traceId);
}

4. Test Metric Resets (resetMetrics)

Clear sliding window buffers and Prometheus counters between test suite runs:

import { resetMetrics } from "@stacklenzz/server";

beforeEach(() => {
  resetMetrics();
});

Exposed Endpoints

| Endpoint | Method | Format | Purpose | |---|---|---|---| | /api/observability/stats | GET | JSON | Feeds real-time operational state, rolling error rates, runtime health, and error lists to the UI | | /metrics | GET | Plaintext | Standard Prometheus scraper endpoint |


Configuration Options

interface ObservabilityConfig {
  serviceName?: string;       // default: "stacklenzz-server"
  environment?: string;       // default: "development"
  instanceId?: string;        // default: "local"
  metricsPath?: string;       // default: "/metrics"
  logLevel?: string;          // default: "info"
  autoInitTracing?: boolean;  // default: true
  ignoredPaths?: string[];    // default: ["/metrics", "/healthz", "/health"]
}

🤝 Contributing & Documentation

Contributions are welcome! Please visit the official Stacklenzz Documentation Portal to explore setup guides, architecture overviews, and usage examples.

To report bugs or contribute code:

  1. Open an issue or Pull Request on GitHub.
  2. Ensure unit tests pass (npm run test:server).

License

Apache License 2.0 © Goodnews Azonubi