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

@theholocron/observability

v0.4.0

Published

Logging, error tracking, and analytics — one interface, swappable backends.

Downloads

20,122

Readme

@theholocron/observability

Logging, error tracking, and analytics — one interface, swappable backends.

Installation

pnpm install @theholocron/observability

Usage

See the documentation for the API.

Installation

pnpm add @theholocron/observability

Then add the peer dependencies for the subpaths you use — they are all optional:

| Subpath | Peers | | -------------------------------------- | -------------------------------------- | | @theholocron/observability/core | none | | @theholocron/observability/logger | pino, pino-pretty, @axiomhq/pino | | @theholocron/observability/errors | @sentry/node | | @theholocron/observability/analytics | posthog-node | | @theholocron/observability/testing | vitest |

Usage

Application modules depend on the interfaces from /core, never a concrete adapter:

import type { Logger, ErrorSink } from "@theholocron/observability/core";

export function deploy(deps: { logger: Logger; errors: ErrorSink }) {
  deps.logger.info({ target: "production" }, "deploying");
}

The process entry point wires the adapters and is the only place that reads credentials:

import { createLogger } from "@theholocron/observability/logger";
import { NoopErrorSink } from "@theholocron/observability/core";
import { SentrySink } from "@theholocron/observability/errors";

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

const errors = process.env.SENTRY_DSN ? new SentrySink() : new NoopErrorSink();
errors.init({
  dsn: process.env.SENTRY_DSN ?? "",
  release: "[email protected]",
  environment: process.env.CI ? "ci" : "local",
  tags: { runId },
});

deploy({ logger, errors });

For the browser, an edge runtime, or React Native, import @theholocron/observability/core (zero dependencies) and use ConsoleLogger from /logger in place of Pino.

Testing code that depends on Logger / ErrorSink / AnalyticsSink? Use the spy doubles from /testing instead of hand-rolling one per repo:

import { fakeLogger, fakeErrorSink } from "@theholocron/observability/testing";

const log = fakeLogger();
const errors = fakeErrorSink();
await deploy({ logger: log, errors, target: "production" });
expect(log.info).toHaveBeenCalledWith(expect.objectContaining({ target: "production" }), "deploying");
expect(errors.captureException).not.toHaveBeenCalled();

For a non-vitest context that just needs a Logger with no output (an example, a non-test opt-out path), use NoopLogger from /core — it discards everything, child() returns itself.

See the documentation for the full API.

Development

| Script | Command | | -------------------- | ------------------------ | | pnpm build | tsdown | | pnpm lint | holocron run lint | | pnpm test | holocron run test | | pnpm test:coverage | vitest run --coverage | | pnpm typecheck | holocron run typecheck | | pnpm audit | knip |

Releases

Automated via semantic-release. See the releases page and CHANGELOG.md.