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 🙏

© 2025 – Pkg Stats / Ryan Hefner

sqljs-documentstore

v1.1.1

Published

Minimal, encrypted, sql friendly typed document store, with support for indexed columns. Protects against transactional conflicts

Readme

sqljs-documentstore

sqljs-documentstore Minimal, encrypted, sql friendly typed document store, with support for indexed columns. Protects against transactional conflicts.
The schema for each table is [id, json, ...indexedColumns]

Install

npm install --save sqljs-documentstore

Usage

exported pieces:

  • Db abstract class, extend it and add TypedDocumentStores for each table => class mapping
  • TypedDocumentStore is meant to map a class type to a table, and has read and write methods
  • LockedDatabase is consumed in TypedDocumentStore. This is a transactional wrapper around sql.js. It handles transactional scope for multiple programmatic writes and ensures locking so separate txns can't collide.
  • sqlHelpers has methods to load, save, etc

Getting started

first, load your database

const sqlJsStatic = await sqlite({ locateFile: (file: string) => `${import.meta.env.BASE_URL}assets/${file}` }); //ensure sql-wasm.wasm is placed in dist/assets/ folder
const {key, database} = await sqljsPersistence.load('mydb', 'mySecretDbKey', sqlJsStatic);

const flush = flushHelpers.createAsyncFlushQueue(() => sqljsPersistence.save('mydb', key, database));
const lockedDatabase = new LockedDatabase(database, flush);

recommend creating a wrapping "DocumentStores" class as shown below:

public class DocumentStores extends Db {
  public CustomerData = new TypedDocumentStore(this.db, 'CustomerData', <CustomerData>{}, {
    name: x => x.name,
    orderCount: x => x.orders?.length
  }).asInterface;

  //... more table declarations

  
  ///////
  private static instance: DocumentStores;
  public static get Instance(): DocumentStores { return this.instance ?? (this.instance = new this()); }
  constructor() { super(lockedDatabase); }
}

usage example

  interface CustomerData {
      id: string;
      name: string;
      address: string;
      orders: any[];//OrderData[];
  }


  function exampleUsage() {
    const db = DocumentStores.Instance;
    const allCustomers = ds.CustomerData.getAll(); // returns CustomerData[]
    
    const dave_id = 'abc123';

    db.txn('create Dave', txnId => {
      db.CustomerData.set(txnId, { id: dave_id, name: 'Dave', address: '1 infinity lp', orders: [{ id: 1, description: 'first order' }]});
    });

    const dave = db.CustomerData.get(dave_id); // returns <CustomerData>
    const maybe_dave = db.CustomerData.tryGet(dave_id); //returns <CustomerData?> assert it's not null before using

    db.txn('update Dave', txnId => {
      db.CustomerData.update(txnId, dave_id, x => {
        x.name += ' the great';
        x.address = 'cloud 9';
      });
    });

    const itemsWithOrders = db.CustomerData.query(x => `where ${x.orderCount} >= ?`, [1]);
    const indexValuesOnly = db.CustomerData.queryIndexes(x => `where ${x.orderCount} > 0`); //fetch just index columns (strongly typed as index type - {id, name, orderCount} in this case) useful if table has large quantities of data and you only need, e.g. the ids that match a query
    const customerIds = new Set(indexValuesOnly.map(x => x.id));
  }

    //use txnAsync when you want to have a transactional scope around actions that are async
  async function exampleUsageAsync() {
    const db = DocumentStores.Instance;
    await db.txnAsync('fetch in the middle of a txn', txnId => {
      const newData = await fetch(.../* actual params go here */);
      db.CustomerData.insertMany(newData); //use insertMany if data is not expected to exist already
      db.CustomerData.setMany(newData); //insert new rows, update if already exist
    });
  }