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

fakebase

v0.3.0

Published

A "fake" database for Node.js that stores data in local JSON files, for testing and sample applications.

Readme

Fakebase

A "fake" database for Node.js that stores data in local JSON files, for testing and sample applications.

Installation

npm install fakebase

Usage

Create a Database instance specifying in which folder to store the data, then create a Table for each type you want to store:

import { Database } from 'fakebase';

const db = new Database('./data/');
const Apple = db.table('apples');
const Orange = db.table('oranges');

This will save apples in ./data/apples.json and oranges in ./data/oranges.json.

You can then manipulate each table using the following CRUD operations:

// create a new record: returns an object with an auto-generated id
const newApple = await Apple.create({ variety: 'Gala', weight: 133 });
// => newApple: { id: 'oY6H7nWVxaT60WJV3iN7M', variety: 'Gala', weight: 133 }

// get all records as an array
const apples = await Apple.findAll();
// => apples: [{ id: 'oY6H7nWVxaT60WJV3iN7M', variety: 'Gala', weight: 133 }]

// find a record by id
const oldApple = await Apple.findById('oY6H7nWVxaT60WJV3iN7M');
// => oldApple: { id: 'oY6H7nWVxaT60WJV3iN7M', variety: 'Gala', weight: 133 }

// update a record
await Apple.update({ id: 'oY6H7nWVxaT60WJV3iN7M', variety: 'Braeburn', weight: 133 });

// delete a record by id
await Apple.delete('oY6H7nWVxaT60WJV3iN7M');

// find the first record matching a predicate function
const bigApple = await Apple.findOne((apple) => apple.weight > 200);

// find all records matching a predicate function
const galaApples = await Apple.findAll((apple) => apple.variety === 'Gala');

That's it. All operations are asynchronous.

JSON files are read once at startup and written after each modification. The assumption is that the Node.js app using Fakebase is the only process modifying those files.

You can manually edit the JSON files to provide some initial data, as long as you do that before starting the application. External changes made while the app is running will not be detected, and will be overwritten if any of create/update/delete is called.

Usage with TypeScript

When using TypeScript you can specify an interface representing the record type stored in each file. E.g.

const { Database, Entity } = require('fakebase');

interface Apple extends Entity {
  variety: string;
  weight: number;
}

const db = new Database('./data');
const Apple = db.table<Apple>('apples'); // Apple: Table<Apple>
const apples = await Apple.findAll(); // apples: Apple[]
const apple = await Apple.findById('oY6H7nWVxaT60WJV3iN7M'); // apple: Apple

The Entity interface simply requires each object to have an id:

export interface Entity {
  id: string;
}

History

This project started as Not a Real DB. It was rewritten to provide async rather than sync APIs, and renamed in the process.

The initial inspiration was JSON Server, but that project keeps all data in a single JSON file and I wanted to store each collection in a separate file instead.