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

@intx/log

v0.5.0

Published

Structured logging with per-package loggers and pluggable development and production sinks

Readme

@intx/log

Thin wrapper around LogTape that the rest of the monorepo uses for structured logging. Re-exports a narrow slice of the LogTape API — only the symbols other @intx/* packages actually use today — and adds a setup() helper that installs the project's preferred development and production sinks.

Every package gets its logger through getLogger; applications call setup() once at startup to choose the output format and override per-category log levels.

Consumers that need a piece of LogTape this package does not re-export should import it from @logtape/logtape directly rather than widen this surface speculatively. Widen it here only when at least one consumer needs the symbol.

import { getLogger, setup } from "@intx/log";

await setup({ dev: true, levels: { "hub.requests": "debug" } });

const logger = getLogger(["hub", "ws", "sidecar"]);
logger.info`Sidecar ${sidecarId} registered`;

Surface

  • @intx/log — getLogger for hierarchical loggers, setup and SetupOptions for application configuration, plus configureSync, getConfig, and resetSync for tests that need to drive LogTape configuration directly. Importing the package also installs the default console sink as a side effect so early diagnostics work before setup() is called. Runtimes without a Node process global use the development formatter by default.
  • @intx/log/hono — Hono middleware re-exported from @logtape/hono for HTTP request logging. Hono is an optional peer dependency; only import this entry point from packages that already pull Hono in.