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

lossy-store

v1.2.4

Published

simple mini database that does not promise durability, for when you do not need it!

Downloads

100

Readme

lossy-store

simple mini database that does not promise durability, for when you do not need it!

It's a key value store, and each value is a file. Each value is stored in it's own file.

api

store = LossyStore(dir, codec?)

create a lossy store with the given codec (or JSON by default) at the dir

store.has(key)

returns true if this key is currently in the store.

store.ensure(key, cb)

ensure that this key is loaded from the file system. if the file has already been read, cb is called immediately. if set is called while waiting for the filesystem, cb is called immediately.

store.get (key, cb)

get the current value for key, loading it if necessary

store.get (key) => value

return the currently set value for key. may be null.

store.set(key, value)

Set a new value. this will trigger a write to be performed (at some point)

License

MIT