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

@indb/stores

v0.3.5

Published

The stores packages exposes several classes that keep an in-memory representation of some part of the database. These in-memory stores are kept up-to-date with the underlying database by subscribing to the `change` events the database instance dispatches.

Downloads

27

Readme

@indb/stores

The stores packages exposes several classes that keep an in-memory representation of some part of the database. These in-memory stores are kept up-to-date with the underlying database by subscribing to the change events the database instance dispatches.

Additionally, since the database instances act as event aggregators for all instances of the database, these in-memory stores stay up to date even when changes occur in other tabs or windows.

API Docs

Example

An example store looks something like this:

import { Database, type SchemaDefinition } from '@indb/database';

type FavoriteColor = 'red' | 'green' | 'blue';

type User = {
  id: string;
  firstName: string;
  lastName: string;
  favorite: {
    color: FavoriteColor;
  };
};

type Tables = {
  users: User;
};

const DATABASE_NAME = 'app';
const SCHEMA: SchemaDefinition<Tables> = {
  version: 1,
  stores: {
    users: {
      keyPath: 'id',
      indices: {
        'lastName': {},
        'favorite.color': {},
      },
    },
  },
};

const database = new Database<Tables>(DATABASE_NAME, SCHEMA);

export const compareUsers = (left: User, right: User): number => {
  const last = left.lastName.localeCompare(right.lastName);
  if (last === 0) {
    return left.firstName.localeCompare(right.firstName);
  }
  return last;
};

// A slice representing all users:
const allUsers = new Slice({
  database,
  storeName: 'users',
  compare: compareUsers,
});

// A slice representing all users whose favorite color is blue:
const blueUsers = new Slice({
  database,
  storeName: 'users',
  compare: compareUsers,
  index: {
    path: 'favorite.color',
    value: 'blue',
  },
});

const smithsCounter = new Counter({
  database,
  storeName: 'users',
  index: {
    path: 'lastName',
    value: 'Smith',
  },
});

Stores

Slice

The slice store represents an ordered-list of objects from an object store. It may be all of the objects in the store, or only those that match an index value.

The slice represents these objects in a Collection data store that is kept up-to-date by subscribing to events from the database object.

The getSnapshot method returns a POJO data structure that looks like:

type CollectionData<T> = {
  ids: Key[];
  index: Record<Key, T>;
};

And the ids list is sorted based on sorting the objects with the compare function.

Counter

The counter store represents a count of objects from a store. It may count all the objects in the store, or just those in an index that match a specific value.

The getSnapshot method returns the count.

Entity

The entity store represents a single record in a single object store. You provide the name of the store and the key, and this store will provide a response represnting the status of the entity (LOADING, FOUND, NOT_FOUND) and, when FOUND, the entity itself.

UseSyncExternalStore

All of the store classes in this package can be used with useSyncExternalStore directly:

const snapshot = useSyncExternalStore(slice.subscribe, slice.getSnapshot);

The react package, and the preact package provide some ready-made hooks for working with slices and counters.