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

@prsm/log

v1.0.2

Published

Structured logging with child contexts

Readme

Structured logging with child contexts. JSON in production, pretty in dev.

Installation

npm install @prsm/log

Usage

import log from '@prsm/log'

log.info('server started', { port: 8080 })
log.warn('slow query', { ms: 1200 })
log.error(new Error('connection refused'))

Pretty output (dev):

[14:32:01] INFO  server started
    port: 8080
[14:32:01] WARN  slow query
    ms: 1200
[14:32:01] ERROR connection refused
    err: connection refused

JSON output (production):

{"level":"info","msg":"server started","port":8080,"ts":1710782521000}

Child Contexts

Create loggers that carry context through a request, job, or connection.

const conn = log.child({ connId: 'abc-123' })
conn.info('command received', { cmd: 'submit' })
// [14:32:01] INFO  command received
//     connId: abc-123
//     cmd: submit

const db = conn.child({ db: 'postgres' })
db.info('query', { ms: 12 })
// [14:32:01] INFO  query
//     connId: c1
//     db: postgres
//     ms: 12

Context accumulates. Every log from a child includes all parent context.

Configuration

log.configure({
  level: 'debug',  // debug | info | warn | error | none
  pretty: false,   // true for human-readable, false for JSON
})

Defaults: level info, pretty when NODE_ENV !== 'production'.

Tracing Across Subsystems

Pass context through queue jobs, realtime commands, workflows.

server.exposeCommand('submit', async (ctx) => {
  const l = log.child({ connId: ctx.connection.id })
  l.info('received')
  await queue.push({ ...ctx.payload, _trace: l.context })
})

queue.process(async (payload, task) => {
  const l = log.child({ taskId: task.uuid, ...payload._trace })
  l.info('processing')
  // every log line carries connId + taskId
})

License

MIT