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

hypercore-logger

v1.4.2

Published

Distributed logger

Downloads

19

Readme

hypercore-logger

Distributed logger

npm install hypercore-logger

Usage

const Logger = require('hypercore-logger')

// pass backing hypercore
const log = new Logger(core)

// add a log message
await log.log({ hello: 'world' })

Setup swarming with Hyperswarm on the core and somewhere else

const log = new Logger(core)

for await (const { timestamp, stats, message } of log.tail()) {
  console.log(timestamp, stats, message)
}

API

Logger

const log = new Logger(core)

Create a new logger backed by a Hypercore (core).

log.discoveryKey

The discoverKey of the Hypercore backing the log.

log.key

The key of the Hypercore backing the log.

await log.ready()

Wait for the log to fully open.

await log.log(...msg)

Log the msg arguments as a string representation intended for debugging, like console.log()'s output.

In addition to the string representation, metadata is automatically added to each log. Each appended to the backing Hypercore will look like:

{
  timestamp: Date.now(),
  stats: Stats,
  subsystem: log.subsystem,
  message: '' // String representation of msg
}

Stats includes:

stats: {
  cpus: number, // Number of avaliable cpus
  cpu: number, // Precent of CPU usage
  cpuThread: number, // Percent of thread usage
  cpuDelay: number, // Event loop delay the last ~5s
  rss: integer, // Resident Set Size
  heapUsed: integer, // Amount of heap used in js engine
  heapTotal: integer, // Total size of heap in js engine
  external: integer, // Memory usage of C++ objects bound to JavaScript objects
}

The block is encoded via the Hyperschema schema @logger/entry.

const stream = log.tail(opts)

Returns a live Readable Stream of the contents of the log. Acts like tail -f on a file, showing new data as it's appended.

  • start: Index of the starting block
  • end: Index of the end block

Example:

for await (const { timestamp, stats, message } of log.tail()) {
  console.log(timestamp, stats, message)
}

await logger.find(opts)

Find start and end blocks to apply filters

  • opts.gte: Start at the first entry with a timestamp >= gte

  • opts.gt: Start at the first entry with a timestamp > gt

  • opts.lte: End before the first entry with timestamp > lte

  • opts.lt: End before the first entry with timestamp >= lt

await log.close()

Fully close the log and the Hypercore backing it.

CLI

Comes with a CLI tool for tailing a hypercore-logger.

npm install -g hypercore-logger
hypercore-logger --key <key>

Usage:

hypercore-logger [flags]

Flags:
  --key, -k <key>       log core key
  --peer, -p <key>      noise key of peer
  --storage, -s <dir>   where to store the core, defaults to /tmp/hypercore-logger
  --help|-h             Show help

License

Apache-2.0