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

@o3osatoshi/logging

v0.1.0

Published

Axiom-first logging helpers for Node, Edge, and browser runtimes.

Readme

@o3osatoshi/logging

Axiom-first logging helpers for Node, Edge, and browser runtimes.

Focus:

  • Small surface area with consistent fields across runtimes
  • Logs + metrics separated into dedicated Axiom datasets
  • Trace context fields (trace_id, span_id) aligned with OpenTelemetry naming
  • Next.js helpers available via @o3osatoshi/logging/nextjs

Install

pnpm add @o3osatoshi/logging

Concepts

  • Datasets
    • datasets.logs and datasets.metrics are required.
    • Logs and metrics are emitted as structured events to their respective datasets.
  • Service and environment
    • Each event includes service.name and deployment.environment.
  • Trace context
    • Request helpers attach trace_id, span_id, and parent_span_id (when available).
    • Incoming traceparent headers are parsed if provided.

Node usage (@o3osatoshi/logging/node)

Initialization

import { initNodeLogger } from "@o3osatoshi/logging/node";

initNodeLogger({
  client: {
    token: process.env.AXIOM_API_TOKEN!,
  },
  datasets: {
    events: "events",
    metrics: "metrics",
  },
  env: "production",
  service: "portfolio-web",
  minLevel: "info",
  flushOnEnd: false,
});

Request-scoped logging

import { withRequestLogger } from "@o3osatoshi/logging/node";

await withRequestLogger(
  {
    clientIp: req.headers.get("x-forwarded-for") ?? undefined,
    httpMethod: req.method,
    httpRoute: "/api/items/:id",
    requestId: req.headers.get("x-request-id") ?? undefined,
    userAgent: req.headers.get("user-agent") ?? undefined,
  },
  async (request) => {
    request.logger.info("http_request_received");

    try {
      // ...your handler...
      request.logger.metric("http.server.requests", 1, {
        "http.method": req.method,
        "http.route": "/api/items/:id",
        "http.status_code": 200,
      }, { kind: "counter", unit: "1" });
    } finally {
      await request.flush();
    }
  },
);

Process-level logging

import { createNodeLogger } from "@o3osatoshi/logging/node";

const log = createNodeLogger();
log.info("server_started", { node_version: process.version });

Edge usage (@o3osatoshi/logging/edge)

import { initEdgeLogger, withRequestLogger } from "@o3osatoshi/logging/edge";

initEdgeLogger({
  client: { token: env.AXIOM_API_TOKEN },
  datasets: { events: "events", metrics: "metrics" },
  env: "production",
  service: "portfolio-edge",
});

await withRequestLogger({ httpMethod: "GET", httpRoute: "/edge/healthz" }, (req) => {
  req.logger.info("edge_request");
});

Browser usage (@o3osatoshi/logging/browser)

import { initBrowserLogger, createBrowserLogger } from "@o3osatoshi/logging/browser";

initBrowserLogger({
  client: { token: process.env.NEXT_PUBLIC_AXIOM_TOKEN! },
  datasets: { events: "events", metrics: "metrics" },
  env: "production",
  service: "portfolio-web",
});

const log = createBrowserLogger();
log.event("page_view", { path: window.location.pathname });

Proxy transport (@o3osatoshi/logging/proxy)

Use the proxy transport when you want to send client logs to your server before ingesting them into Axiom (for example, to avoid exposing tokens).

Client-side (browser)

import { initBrowserLogger } from "@o3osatoshi/logging/browser";
import { createProxyTransport } from "@o3osatoshi/logging/proxy";

initBrowserLogger({
  transport: createProxyTransport({
    url: "/api/logging",
    flushIntervalMs: 1000,
  }),
  datasets: { events: "events", metrics: "metrics" },
  env: "production",
  service: "portfolio-web",
});

Server-side (Edge/Node)

import { createEdgeProxyHandler } from "@o3osatoshi/logging/edge";

export const POST = createEdgeProxyHandler({
  allowDatasets: (process.env.LOGGING_ALLOWED_DATASETS ?? "logs,metrics").split(
    ",",
  ),
});

Node runtimes can use createNodeProxyHandler from @o3osatoshi/logging/node.

Custom transport

Runtime helpers accept a custom transport if you want to swap away from Axiom:

import { initNodeLogger } from "@o3osatoshi/logging/node";

initNodeLogger({
  transport: customTransport,
  datasets: { events: "events", metrics: "metrics" },
  env: "production",
  service: "portfolio-web",
});

Axiom helpers (@o3osatoshi/logging/axiom)

import { createAxiomTransport } from "@o3osatoshi/logging/axiom";
import { createLogger } from "@o3osatoshi/logging";

const transport = createAxiomTransport({
  token: process.env.AXIOM_API_TOKEN!,
  mode: "batch",
});

const logger = createLogger({
  attributes: { "service.name": "portfolio-web" },
  datasets: { events: "events", metrics: "metrics" },
  transport,
});

Next.js helpers (@o3osatoshi/logging/nextjs)

Requires Next.js and React in the consuming app. Client helpers (Web Vitals, createUseLogger) live in @o3osatoshi/logging/nextjs/client.

import {
  createOnRequestError,
  createRouteHandler,
  logMiddlewareRequest,
} from "@o3osatoshi/logging/nextjs";
import { createWebVitalsComponent } from "@o3osatoshi/logging/nextjs/client";
import { createBrowserLogger, initBrowserLogger } from "@o3osatoshi/logging/browser";
import { createNodeLogger, initNodeLogger } from "@o3osatoshi/logging/node";
import { NextResponse } from "next/server";

initNodeLogger({
  client: { token: process.env.AXIOM_API_TOKEN! },
  datasets: { events: "events", metrics: "metrics" },
  env: "production",
  service: "portfolio-web",
});

initBrowserLogger({
  client: { token: process.env.NEXT_PUBLIC_AXIOM_TOKEN! },
  datasets: { events: "events", metrics: "metrics" },
  env: "production",
  service: "portfolio-web",
});

const serverLogger = createNodeLogger();
const clientLogger = createBrowserLogger();
export const withAxiom = createRouteHandler(serverLogger);
export const onRequestError = createOnRequestError(serverLogger);
export const WebVitals = createWebVitalsComponent(clientLogger);

export const GET = withAxiom(async () => {
  return NextResponse.json({ ok: true });
});

export async function middleware(request: Request) {
  logMiddlewareRequest(serverLogger, request);
  return NextResponse.next();
}

Client components can use createUseLogger from @o3osatoshi/logging/nextjs/client.