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

level-change-processor

v1.0.0

Published

follows a changes-feed and processes each entry, storing state in a leveldb

Downloads

9

Readme

level-change-processor

NPM

Build Status dat

Follows a changes-feed and processes each entry, storing state in a levelup. Automatically handles resuming the changes processing from where it left off when restarted.

Designed for creating secondary indexes with leveldb but can be used in many different applications.

Usage

require('level-change-processor')(opts)

Construct a new change processor instance.

opts is an object:

  • db (required) - a levelup to store the change state in
  • feed (required) - a changes-feed instance
  • worker (required) - a function (see below) that processes each change
  • key (default latest) - a key to use to store the change state in the db above
  • dbOptions (default {valueEncoding: 'utf8'}) - options to pass to the db .get and .put calls

example:

var processor = changeProcessor({
  db: stateDb,
  feed: feed,
  worker: worker
})

Worker function

A function that takes two arguments: (change, cb).

change will be an object with these properties:

  • change - this will be a js Number that increments by 1 for every change, starting at 1
  • value - this will be the change payload that the changes feed writes to you. usually is a Buffer but depends on the feed

These are the two guaranteed properties. There may be other properties on change depending on the feed.

error handling

To catch errors attach a processor.on('error', errorHandler) event