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

lildata

v1.0.1

Published

When you need the opposite of big data.

Downloads

9

Readme

Lil Data

When you need the opposite of big data.

What

A small, loosly persisted javascript Map. Since everything is fitted in a JS object, your data should be small, few megabytes at most. All writes are async and flushed every 250ms, loosing data in that time frame must be acceptable or use something else.

Why

Because sometimes you just want to save the state of your app and even pulling sqlite would be overkill.

  • Little overhead on js native Map so it's fairly fast
  • Simple

    This solution fit in 100 lines of code.

How

Usage:

// init the table
// will use the name of the file +.json if import.meta is used
const users = persist(import.meta, { primary: 'id' }) // optional
const users = persist('/path/to/some/file')

// adding data, objects only with the primary key
users.put({
	id: 1,
	name: 'Chris',
	birthDate: '1988-05-11',
})

// removing data
users.del(1)
users.del({ id: 1 }) // or

// wait for next batch write
await users.sync()

// get by primary key
const chris = user.get(1)

// query data
const chris = users.find(user => user.name === 'Chris')

// query multiple elements
const users.filter(user => user.birthDate.startsWith('1988'))

// synchronous cleanup the data file (destroy changes history)
users.vacum()