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 🙏

© 2024 – Pkg Stats / Ryan Hefner

hyperbee-diff-stream

v1.0.3

Published

Get the diff stream between two versions of a hyperbee (supports autobase views)

Downloads

63

Readme

Hyperbee Diff Stream

Get the diff stream between two snapshots of a hyperbee. Ideal for autobase views.

For example, when reconnecting after having worked locally for a while, it can get the diff stream between a snapshot from just before and from just after the autobase linearisation. Even if several peers (including you in your local fork) made a lot of changes to a particular key, the diff stream will still yield only a single change for it.

Install

npm i hyperbee-diff-stream

Compatibility

Uses features introduced in Hyperbee ^2.5.0, Hypercore ^10.8.1 and autobase^6.0.0-rc3

Usage

See example.js

API

const diffStream = new BeeDiffStream(leftSnapshot, rightSnapshot, [options])

Make a new BeeDiffStream instance, which is the stream of changes to get from the state of leftSnapshot to that of rightSnapshot.

The stream is ordered by key.

leftSnapshot and rightSnapshot should be snapshots (or checkouts) of the same hyperbee. The hyperbee can be an autobase view.

The passed snapshots are managed by BeeDiffStream, and will be closed when the diff stream closes.

The opts include:

{
  gt: 'only consider keys > than this',
  gte: 'only consider keys >= than this',
  lt: 'only consider keys < than this',
  lte: 'only consider keys <= than this',
  keyEncoding: 'utf-8', // a key encoding
  valueEncoding: 'json' // a value encoding,
  closeSnapshots: true // set to false if you wish to use the passed-in snapshots after the diffStream is fully yielded.
}

By default the key- and value encoding of the hyperbee are used.

The stream yields values which have the same format as a Hyperbee diff stream:

{
   left: { seq, key, value },
   right: { seq, key, value }
}

left is the current entry, right is the previous entry.

  • if right is null, the key was added
  • If left is null, the key was deleted
  • If both left and right are present, the key was updated from right to left.

Note: when used on an autobase view, it might be tricky to interpret the seq value, since it can refer to either the left or the right snapshot. (With autobase views, blocks can get removed due to truncates, so the same seq might refer to different entries on different snapshots.)