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-atomic-counter

v0.1.0

Published

Accurately keep count of entries in a levelup store.

Downloads

2

Readme

level-atomic-counter

npm

Accurately keep count of entries in a levelup store with sublevel installed. It does this by monkey-patching put/del/batch to check whether a key already exists or not before appending the new count to the batch of operations being written. The count is stored in a sublevel named 'counter'.

Note: The chained form a batch() is not supported.

let level = require('level')
let sublevel = require('level-sublevel');
let db = sublevel( level('example.db') );

let Counter = require('level-atomic-counter');
Counter.install(db);

db.batch([
	{type: 'put', key: 1, value: 1},
	{type: 'put', key: 2, value: 2},
	{type: 'del', key: 1},
], (err) => {
	db.getCount((err, result) => {
		console.log(result); // 1
	});
});

Methods

let counter = require('level-atomic-counter')(db);

This does not alter the db object and instead returns an object of methods in the form of {put, del, batch, getCount, recount} which will update the counter only when used.

require('level-atomic-counter').install(db);

This will install the methods onto the db object directly instead of returning them. Do it this way if you want all writes to the database to update the counter so long as those writes use this this particular db object.

counter.getCount(callback(Error, Number))
counter.recount(callback(Error, Number))

License

MIT