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

@polkadot-apps/logger

v0.1.5

Published

Structured, namespace-filtered logging for the @polkadot-apps ecosystem

Readme

@polkadot-apps/logger

Structured, namespace-filtered logging for the @polkadot-apps ecosystem.

Install

pnpm add @polkadot-apps/logger
# or
npm install @polkadot-apps/logger

No additional dependencies required.

Quick Start

import { createLogger } from "@polkadot-apps/logger";

const log = createLogger("my-module");

log.error("connection failed", { endpoint: "wss://rpc.polkadot.io" });
log.warn("retry limit approaching", { attempt: 3, max: 5 });
log.info("connected", { chain: "Polkadot" });
log.debug("block received", { number: 21_000_000 });

The default log level is "warn", so only error and warn messages are emitted out of the box.

Basic Usage

Each logger is scoped to a namespace. Namespaces appear in every log entry, making it straightforward to trace output back to the originating module.

import { createLogger } from "@polkadot-apps/logger";

const rpcLog = createLogger("rpc");
const txLog = createLogger("tx-pool");

rpcLog.info("subscribed to new heads");
txLog.debug("pending extrinsic", { hash: "0xabc..." });

Configuration

Use configure to change the global log level, filter by namespace, or install a custom handler.

import { configure } from "@polkadot-apps/logger";

configure({
  level: "debug", // show all messages
});

Set Level and Namespace Filter

import { configure } from "@polkadot-apps/logger";

configure({
  level: "info",
  namespaces: ["rpc", "tx-pool"], // only these namespaces emit
});

Environment Variables

You can configure logging without code changes by setting environment variables before the process starts.

| Variable | Purpose | Example | |---|---|---| | POLKADOT_APPS_LOG | Set the global log level. | POLKADOT_APPS_LOG=debug | | POLKADOT_APPS_LOG_NS | Comma-separated list of namespaces to include. | POLKADOT_APPS_LOG_NS=rpc,tx-pool |

Environment variables are read once at initialization. Calling configure overrides them.

Custom Handlers

Replace the default console output with any function that accepts a LogEntry.

import { configure } from "@polkadot-apps/logger";
import type { LogEntry } from "@polkadot-apps/logger";

configure({
  handler: (entry: LogEntry) => {
    // Send to an external service
    fetch("/api/logs", {
      method: "POST",
      body: JSON.stringify(entry),
    });
  },
});

Structured JSON Logging

import { configure } from "@polkadot-apps/logger";

configure({
  level: "debug",
  handler: (entry) => {
    process.stdout.write(JSON.stringify(entry) + "\n");
  },
});

Namespace Filtering

When namespaces is set, only loggers whose namespace appears in the list produce output. All other loggers are silenced regardless of log level.

import { configure, createLogger } from "@polkadot-apps/logger";

configure({ level: "debug", namespaces: ["rpc"] });

const rpcLog = createLogger("rpc");
const uiLog = createLogger("ui");

rpcLog.debug("this is emitted"); // visible
uiLog.debug("this is silenced"); // filtered out

API

| Function | Signature | Description | |---|---|---| | createLogger | (namespace: string) => Logger | Create a namespaced logger with error, warn, info, and debug methods. | | configure | (config: LoggerConfig) => void | Set the global log level, namespace filter, and/or custom handler. |

Types

/** Log severity levels, ordered from most to least severe. */
type LogLevel = "error" | "warn" | "info" | "debug";

/** A single structured log entry. */
interface LogEntry {
  level: LogLevel;
  namespace: string;
  message: string;
  data?: unknown;
  timestamp: number;
}

/** A function that receives log entries for custom output. */
type LogHandler = (entry: LogEntry) => void;

/** Global logger configuration. */
interface LoggerConfig {
  /** Minimum severity to emit. Default: "warn". */
  level?: LogLevel;
  /** When set, only matching namespaces produce output. */
  namespaces?: string[];
  /** Replace the default console handler. */
  handler?: LogHandler;
}

/** A namespaced logger instance. */
interface Logger {
  error(message: string, data?: unknown): void;
  warn(message: string, data?: unknown): void;
  info(message: string, data?: unknown): void;
  debug(message: string, data?: unknown): void;
}

License

Apache-2.0