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

@knowark/loggarkjs

v0.5.0

Published

Utilitarian Logging Library

Readme

loggark

Utilitarian Logging Library

Logger output format

Logger now emits a single JSON object per log line by default (JSON Lines). This format is easier to consume with journalctl pipelines (jq, grep, field selection).

  • Default: format: 'json'
  • Backward compatibility: format: 'plain'
  • Context flattening in JSON mode: flat: true (default)

Example:

import { Logger } from '@knowark/loggarkjs'

const logger = new Logger({ namespace: 'api' })
logger.info('User login', { userId: 'u-123' })

Outputs:

{"timestamp":"2025-02-15T00:00:00.000Z","level":"info","namespace":"api","message":"User login","userId":"u-123"}

Additional object parameters are merged into the base log object. If keys collide, later merged values overwrite earlier keys.

If you prefer context keys at top level (for simpler jq filters), enable flattening:

const logger = new Logger({
  namespace: 'api',
  context: { correlationId: 'ABCD1234', interactor: 'Informer' },
  flat: true
})

logger.info('User login')
{"timestamp":"2025-02-15T00:00:00.000Z","level":"info","namespace":"api","correlationId":"ABCD1234","interactor":"Informer","message":"User login"}

To keep nested context under context, disable flattening:

const logger = new Logger({
  context: { correlationId: 'ABCD1234' },
  flat: false
})

Journald integration

Set the boolean globalThis.JOURNALD flag to true and Logger will open /run/systemd/journal/socket for you. Every JSON record is translated into Journald fields (PRIORITY, MESSAGE, LEVEL, optional SYSLOG_IDENTIFIER, and uppercased context payloads), so you can pipe logger.info() calls directly into journalctl for centralized viewing.

globalThis.JOURNALD = true
const logger = new Logger({ namespace: 'api' })

logger.info('User login', { userId: 'u-123', extra: undefined })

Undefined values are dropped, null turns into the string 'null', and functions/symbols are rendered so Journald receives a predictable payload. The socket connection is cached per process, so later Logger instances reuse the same transport without extra setup.