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

shared-event-log

v0.4.1

Published

Event log shared betweeen two peers with deterministic references

Readme

shared-event-log

An event log that is shared betweeen two peers with deterministic references.

Usage

API

const log = new Log(id, [opts])

Instantiate a new Log with a given id

Options must include either store or storage:

{
  store, // corestore instance
  storage // storage for a new corestore
}

await log.loadRemote(remoteFeedKey)

Load the remote peer's hypercore

const event = await log.get(clock)

Returns a boolean whether a clock was generated by the local key or not.

await log.append(data)

Append data to the log.

const clock = log.clock()

Get the current clock.

for await (const event of log.getState(start, end))

Returns an async generator of all events added between two clocks: start and end.

Note: The set of updates will be the same for either peer, but the ordering may differ.

const isBefore = log.compare(a, b)

Returns a boolean of whether clock a is ordered before clock b or not.

const clock = log.union(a, b)

Returns a clock that is the union of two clocks. This clock in turn references the union of all events referenced by either clock.

const isLocal = log.isLocal(clock)

Returns a boolean whether a clock was generated by the local key or not.