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

dstate

v0.1.3

Published

Store changing state data as commits that can be rolled back

Readme

dstate

npm version Build Status Dependency Status

Store changing state data as commits that can be rolled back

dstate is used to save state data history in a LevelUP database as commit objects. Each commit is stored as a delta of the state, so you can efficiently store many commits.

Usage

npm install dstate

var DState = require('dstate')

// db is a levelup instance
var ds = new DState(db)

// commit some states
ds.commit({ foo: 'bar', baz: [ 0, 1, 2 ] })
ds.commit({ foo: 'bar2', baz: [ 1, 2, 3 ] })
ds.commit({ foo: 'bar3', baz: [ 2, 3, 4 ], lol: true })

// get current state
ds.getState((err, state) => { ... })

// roll back to first commit
ds.rollback(0)

// remove the first 2 commits
ds.prune(1)

new DState(db)

Creates a DState which stores data in db.

db should be a LevelUp instance. The db should not be shared (if necessary, use level-sublevel to create a sub-section of your db).


state.commit(state, [opts], [callback])

Creates a commit that changes the state to state.

opts may contain:

  • tx Level Transaction (default: null) - If provided, the database operations for this commit will be made via tx (so consistency can be ensured with other db operations).

callback is called with callback(err, index) where index is a number representing the index of the commit that was made.


state.rollback(index, [opts], [callback])

Reverts the state to what is was in the commit with index index.

index should be a number, where 0 is the first commit, etc. It must be less than the index of the most recent commit.

opts may contain:

  • tx Level Transaction (default: null) - If provided, the database operations for this commit will be made via tx (so consistency can be ensured with other db operations).

state.getState(callback)

Calls callback(err, state) with the current state. If no state has been committed yet, state will be null.


state.getIndex(callback)

Calls callback(err, index) with the latest commit index (a number, incrementing on each commit). If no state has been committed yet, index will be null.


state.prune(index, [opts], [callback])

Removes all the commits up to index index (inclusive). The state will not be able to be rolled back to the pruned commits.

index should be a number, where 0 is the first commit, etc. It must be less than the index of the most recent commit.

opts may contain:

  • tx Level Transaction (default: null) - If provided, the database operations for this commit will be made via tx (so consistency can be ensured with other db operations).