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

@viktorbarzin/log

v0.1.0

Published

JSON-lines logger for the homelab app platform: ts, level, logger, msg, extras, exc.

Readme

@viktorbarzin/log

A JSON-lines logger for the platform's log contract: one object per line on stderr with ts (Python isoformat, +00:00), level, logger, msg, then the call's extras (which never overwrite those four keys), then exc for an error. No dependencies; works on Bun and Node.

import { getLogger, installJsonConsole } from "@viktorbarzin/log";

const log = getLogger("myapp.sync");
log.info("sync served", { user: "someone", lists: 3 });
log.exception("sync failed", err, { path: "/api/sync" });

installJsonConsole(); // console.* from the framework becomes JSON lines too (logger "console")
{"ts":"2026-10-16T04:05:06.789000+00:00","level":"INFO","logger":"myapp.sync","msg":"sync served","user":"someone","lists":3}

API

| Export | | |---|---| | getLogger(name) | debug, info, warning, error, exception(msg, err, extra?), record(level, msg, extra?, err?) | | parseLogLevel(raw) | WARN → WARNING; unknown or unset → INFO | | setLogLevel(level) | the threshold; starts from LOG_LEVEL | | setLogSink(sink) | send lines elsewhere (tests); returns a restore function | | installJsonConsole(target?) | route console.* through the logger; an Error argument goes under exc; returns a restore function | | formatRecord, pythonIsoTimestamp | the formatting, exported for tests |

The sink and threshold are one per process (kept on globalThis), so a server bundled twice still logs through one sink. LOG_LEVEL is the only environment variable read.