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

log-bundle

v1.7.2

Published

Production-ready logging and error handling library for Node.js with Pino, Sentry, and Fastify integration

Readme

log-bundle

Production-ready logging and error handling library for Node.js with Pino, Sentry, and Fastify integration.

Features

  • Structured Logging - Built on Pino for high-performance JSON logging
  • Error Handling - RFC 9457 compliant error responses with predefined error types
  • Zod Integration - Automatic validation error formatting with detailed field-level errors
  • Sentry Integration - Automatic error tracking and performance monitoring
  • Fastify Support - First-class Fastify middleware and error handlers
  • Type Safety - Full TypeScript support with comprehensive types
  • Zero Config - Sensible defaults that work out of the box
  • Production Ready - Optimized for performance and reliability

Installation

npm install log-bundle

Optional peer dependencies:

npm install @sentry/node fastify zod

Quick Start

import * as Sentry from "@sentry/node";
import { logConfig, createLogger, setupProcessErrorHandlers, createErrorPipe, notFound } from "log-bundle";
import fastify from "fastify";

// 1. Initialize Sentry (optional, must be first)
if (process.env.SENTRY_DSN) {
  Sentry.init({
    dsn: process.env.SENTRY_DSN,
    environment: process.env.NODE_ENV || "development",
    tracesSampleRate: 0.1,
  });
  logConfig.enableSentry = true;
}

// 2. Create logger
const logger = createLogger({
  level: process.env.LOG_LEVEL || "info",
});

// 3. Setup process error handlers
setupProcessErrorHandlers(logger);

// 4. Create Fastify app
const app = fastify({ logger });

// 5. Define routes
app.get("/users/:id", async (request, reply) => {
  const user = await db.users.findById(request.params.id);

  if (!user) {
    return reply.code(404).send(notFound("user", request.params.id));
  }

  return user;
});

// 6. Setup error handler (must be last)
app.setErrorHandler(
  createErrorPipe(logger, {
    environment: process.env.NODE_ENV,
  })
);

// 7. Start server
await app.listen({ port: 3000 });

Core Concepts

Logging

Create a logger with Pino integration:

import { createLogger } from "log-bundle";

const logger = createLogger({
  level: "info",
});

logger.info("Application started");
logger.warn({ userId: "123" }, "Suspicious activity");
logger.error(error, "Failed to process request");

Log and send to Sentry simultaneously:

logger.errorWithSentry(
  { userId: "123", action: "payment" },
  "Payment processing failed"
);

Error Handling

Use factory functions to create structured errors with clear separation of public (user-facing) and internal (logs/Sentry) data:

import { notFound, validation, internal, database } from "log-bundle";

// Simple errors - basic usage
const error = notFound("user", userId);
const error = validation("Email is required", "email");

// Add internal context (for logs/Sentry only)
const error = notFound("user", userId, {
  internal: { context: { requestId: "abc123", ip: "192.168.1.1" } }
});

// Add public metadata (sent to users)
const error = notFound("user", userId, {
  public: { meta: { suggestion: "Check the user ID format" } }
});

// Capture original errors for Sentry
try {
  await db.query();
} catch (err) {
  const error = database("Query failed", {
    public: { detail: "Unable to fetch data" },
    internal: {
      cause: err, // Original error goes to Sentry only
      context: { query: "SELECT * FROM users", params: { id: userId } }
    }
  });
}

Add context using utilities:

import { notFound, withContext } from "log-bundle";

let error = notFound("user", userId);
error = withContext(error, {
  requestId: "abc123",
  timestamp: new Date().toISOString(),
}); // Adds to internal.context

Fastify Integration

The middleware order matters. Here's the correct setup:

import fastify from "fastify";
import { createLogger, createErrorPipe, createZodValidatorCompiler } from "log-bundle";
import { z } from "zod";

const app = fastify({ logger: createLogger() });

// 1. Register Zod validator (optional, for automatic validation)
app.setValidatorCompiler(createZodValidatorCompiler());

// 2. Register plugins
await app.register(import("@fastify/cors"));

// 3. Register routes
app.get("/", async () => ({ hello: "world" }));

// 4. Register error handler (MUST BE LAST)
app.setErrorHandler(
  createErrorPipe(logger, {
    environment: process.env.NODE_ENV,
  })
);

Use ErrorFactory for automatic request context:

import { ErrorFactory } from "log-bundle";

app.get("/users/:id", async (request, reply) => {
  const errors = ErrorFactory.forRequest(request);

  const user = await db.users.findById(request.params.id);

  if (!user) {
    // Error automatically includes requestId, url, method, ip in internal context
    return reply.code(404).send(errors.notFound("user", request.params.id));
  }

  return user;
});

// You can also pass additional options
app.post("/users", async (request, reply) => {
  const errors = ErrorFactory.forRequest(request);

  try {
    const user = await db.users.create(request.body);
    return user;
  } catch (err) {
    return reply.code(500).send(
      errors.database("Failed to create user", {
        internal: { cause: err }, // Original error for Sentry
        public: { detail: "Unable to create user account" }
      })
    );
  }
});

Sentry Integration

Initialize Sentry at the top of your entry file:

import * as Sentry from "@sentry/node";
import { logConfig } from "log-bundle";

Sentry.init({
  dsn: process.env.SENTRY_DSN!,
  environment: process.env.NODE_ENV!,
  tracesSampleRate: 0.1,
});

logConfig.enableSentry = true;

Control what gets sent to Sentry:

import { errorConfig } from "log-bundle";

// Send all 5xx errors (default)
errorConfig.setSentryStatusRules([[500, 599]]);

// Send all 4xx and 5xx errors
errorConfig.setSentryStatusRules([[400, 499], [500, 599]]);

// Send specific status codes
errorConfig.setSentryStatusRules([500, 502, 503, 504]);

// Send all 5xx except 502 and 503 (e.g., skip proxy/gateway errors)
errorConfig.setSentryStatusRules([{ range: [500, 599], exclude: [502, 503] }]);

// Mix ranges and specific codes
errorConfig.setSentryStatusRules([429, [500, 599]]);

Skip Sentry for specific errors:

import { withoutSentry, notFound } from "log-bundle";

// Using utility
let error = notFound("user", userId);
error = withoutSentry(error);

// Or directly in factory
const error = notFound("user", userId, { skipSentry: true });

Zod Validation

Automatic validation error formatting with Fastify:

import { z } from "zod";
import { createZodValidatorCompiler, createErrorPipe } from "log-bundle";

// Set up validator compiler
app.setValidatorCompiler(createZodValidatorCompiler());
app.setErrorHandler(createErrorPipe(logger));

// Use Zod schemas in routes
app.post("/users", {
  schema: {
    body: z.object({
      email: z.string().email(),
      age: z.number().min(18),
    }),
  },
  handler: async (request, reply) => {
    // request.body is typed and validated
    return { success: true };
  },
});

// Automatic RFC 9457 error response on validation failure (422):
// {
//   "type": "urn:problem:validation",
//   "title": "Validation Error",
//   "status": 422,
//   "detail": "Request validation failed",
//   "errors": [
//     {
//       "field": "email",
//       "message": "Invalid email",
//       "meta": { "code": "invalid_string", "validation": "email" }
//     }
//   ]
// }

See Zod Validation Guide for complete documentation.

Process Error Handlers

Catch uncaught exceptions and rejections:

import { setupProcessErrorHandlers } from "log-bundle";

setupProcessErrorHandlers(logger, {
  exitOnUncaughtException: process.env.NODE_ENV === "production",
  exitOnUnhandledRejection: false,
  onBeforeExit: async () => {
    await db.close();
    await cache.disconnect();
  },
});

Available Error Types

| Function | HTTP Status | Use Case | |----------|-------------|----------| | notFound(resource, id) | 404 | Resource not found | | validation(message, field) | 400 | Input validation failure | | badInput(message) | 400 | Malformed request data | | unauthorized(reason) | 401 | Authentication required | | forbidden(resource, reason) | 403 | Permission denied | | conflict(resource, reason) | 409 | Resource conflict | | internal(message) | 500 | Internal server error | | database(message) | 500 | Database operation failure | | external(service, message) | 502 | External service failure | | timeout(operation, duration) | 504 | Operation timeout | | busy(message) | 503 | Service unavailable |

API Reference

Logger

createLogger(config?: LoggerConfig, transport?: DestinationStream, addSource?: boolean): LoggerWithSentry

Error Factories

notFound(resource: string, id?: unknown, options?: CreateErrorDataOptions): ErrorData
validation(message: string, field?: string, options?: CreateErrorDataOptions): ErrorData
database(message: string, options?: CreateErrorDataOptions): ErrorData
internal(message: string, options?: CreateErrorDataOptions): ErrorData
// ... and more

// CreateErrorDataOptions:
type CreateErrorDataOptions = {
  public?: {
    title?: string;
    detail?: string;
    instance?: string;
    meta?: Record<string, unknown>;
    validationErrors?: ValidationError[];
  };
  internal?: {
    cause?: Error;
    context?: Record<string, unknown>;
    tags?: Record<string, string>;
  };
  httpStatus?: number;
  skipSentry?: boolean;
}

Error Utilities

toHttpResponse(error: ErrorData): { statusCode: number; body: ErrorResponse }
toErrorResponse(error: ErrorData, baseUrl?: string): ErrorResponse
withContext(error: ErrorData, context: Record<string, unknown>): ErrorData
withHttpStatus(error: ErrorData, statusCode: number): ErrorData
withoutSentry(error: ErrorData): ErrorData
isClientError(error: ErrorData): boolean
isServerError(error: ErrorData): boolean

Fastify Handlers

createErrorPipe(logger: Logger, options?: ErrorPipeOptions): FastifyErrorHandler
createFastifyErrorHandler(logger: Logger, options?: FastifyErrorHandlerOptions): FastifyErrorHandler

Sentry

isSentryInitialized(): boolean
sendToSentry(level: Level, logObj: any, message: string, options?: SentrySendOptions): void

Note: Initialize Sentry using @sentry/node directly, then enable it with logConfig.enableSentry = true.

Process Handlers

setupProcessErrorHandlers(logger: Logger, options?: ProcessErrorHandlerOptions): void

Documentation

Examples

See the examples directory for complete working examples:

  • Basic setup with Fastify
  • Error handling patterns
  • Sentry integration
  • Advanced configuration

Requirements

  • Node.js >= 20.0.0
  • TypeScript >= 5.0 (for TypeScript projects)

Performance

log-bundle is optimized for production use:

  • Zero overhead when features are disabled
  • Lazy initialization of expensive resources
  • Native Date methods for timestamp generation (no external dependencies)
  • Pre-compiled regexes and cached values
  • Optimized string operations in hot paths

Author

aeternitas-infinita

Repository

https://github.com/aeternitas-infinita/log-bundle-ts