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

@vargr/vargr-dbai

v0.1.0

Published

**One API, all the databases.**

Readme

Vargr DBai

One API, all the databases.

This is a simplified API that allows one to do all common CRUD methods on a variaty of databases using the same API. This is not and ORM, or a query builder, but has features from both.

The gain is the abillity to write generic layers for Auth, Rest, Validation etc. will work across databases. The price, is an overhead in translating queries and results, as well as not being able to do complex queries.

Storage integrations

  • LowDB
  • MongoDB
  • Sequalize (Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server)
    • This might get deprecated as Knex does the same, but simpler.
  • Knex (Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server)

Todo:

  • Add optional soft delete (on by default)
  • Use symbols instead of strings for query operations ($or, $like, et..)
  • Documentation
  • Consider adding support for immutable documents/rows
  • Test suite refactor
  • More testing...
  • Performance comparison and improvements
  • Pick new integrations, Redis, CouchDB..??
    • https://insights.stackoverflow.com/survey/2019?utm_source=so-owned&utm_medium=announcement-banner&utm_campaign=dev-survey-2019#technology-_-most-loved-dreaded-and-wanted-databases
  • Are there any common missing use cases?
    • Nested document support on document update (update included related)
    • Transaction support

Architectural vision

All interfaces are normalized with a single test suite to keep the same API. The reasoning is to keep this project small and modular.

The shared test suite will ensure sensible defaults for all interfaces. These defaults are to keep configuration to a minimum, and allow more rapid development.