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

@openknot-ts/pino-logging

v0.0.6-preview

Published

Writes OpenKnot logging records through the application's pino instance.

Readme

@openknot-ts/pino-logging

Implements OpenKnot's logging contract over the application's pino instance, which keeps its own options, transports and lifecycle. Consumers keep requiring logger; this module replaces the console default.

The peers are @openknot-ts/logging and pino >=10 <11. The root entry runs without Wire; /wire composes it as a module.

Usage

import { logger } from "@openknot-ts/logging/wire";
import { providePinoLogging } from "@openknot-ts/pino-logging/wire";
import { pino } from "pino";

const nativeLogger = unit({ factory: () => pino({ level: "trace" }) });

const logs = providePinoLogging({
  requirements: { nativeLogger },
  factory: ({ nativeLogger }) => nativeLogger,
});

const renameRole = command<RenameRole>()({
  requirements: { saveRole, logger },
  run: async (input, ctx) => {
    ctx.logger.info("renaming role", { roleId: input.id });
    return success(await ctx.saveRole(input));
  },
});

// defineApplication({ inputs: [renameRoleEndpoint], modules: [applicationModule, nativeLogger, logs] })

The handler's code stays the same as with the console default; pino writes the record as one JSON line, and with tracing bound it also carries traceId and spanId:

{"level":30,"time":1794430107231,"pid":4242,"hostname":"api-1","roleId":"r1","msg":"renaming role"}
  • LOG_LEVEL selects records before they reach pino; keep the instance's own level at trace so it does not drop them again. Each level maps to pino's method of the same name.
  • Attributes become pino's merging object and the message becomes msg. An error attribute is serialized with pino's standard error serializer.
  • The module provides logging only when its requirements are registered; otherwise the console default stays.
  • Flushing an asynchronous destination on shutdown belongs to the instance's owner, for example a resource whose release() flushes it.

API

| Entry | Export | Description | | --- | --- | --- | | root | pinoLogging(instance) | The Logging implementation, without Wire. | | /wire | providePinoLogging({ requirements?, factory }), PinoLoggingOptions | Provides the implementation as a module. |