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

isostore

v1.0.1

Published

A simple isomorphic key-value store with a Map-like API for persisting data.

Downloads

17

Readme

IsoStore

A simple isomorphic key-value store with a Map-like API for persisting data.

Features

  • All stores run everywhere, they just have different backends under the hood.
  • All stores are not intended for performance-critical use cases, since the entire store is saved when a change is made in it.
  • Store saves are batched automatically within a microtask, so performance is not as bad as it could be.
  • When instantiating multiple stores of the same type and with the same id you'll actually always receive the same instance back.
  • Only alphanumeric store ids are allowed, the library will throw on invalid ids.

Stores

The following stores are provided:

  • AbstractStore: A generic store with no backend, for using a custom persistence mechanism.
  • MemoryStore: An in-memory store, useful if you don't need persistence, but you want to use the same API.
  • LocalStore: A store for persisting data reliably and indefinitely.
    • Node: it will atomically write a file to disk, in a non-temporary path that depends on your OS.
    • Browser: it will use the localStorage API.
  • SessionStore: A store per persisting data somewhat unreliably and/or not indefinitely.
    • Node: it will non-atomically write a temporary file to disk, which could be deleted at any time.
    • Browser: it will use the sessionStorage API.

Install

npm install --save isostore

Usage

import {AbstractStore, LocalStore, MemoryStore, SessionStore} from 'isostore';

// Creating a local store, for indefinite persistence

const store = new LocalStore ( 'my-store' ); // The id of the store decides the name of the file on disk

store.has ( 'foo' ); // => false
store.set ( 'foo', 'some_string' ); // => store
store.get ( 'foo' ); // => 'some_string'
store.delete ( 'foo' ); // => true

// Creating another local store, with the same id

const store2 = new LocalStore ( 'my-store' );

console.log ( store === store2 ); // => true, with 🌈 magic 🌈

// Creating a session store, for temporary persistence

const store3 = new SessionStore ( 'my-store' );

// Creating an in-memory store, for no persistence

const store4 = new MemoryStore ();

// Creating a custom store, with a custom backend

const MY_BACKEND = { // It's important to define this outside of the store class
  read ( id ) {
    // Return a [string, string][]
  },
  write ( id, entries ) {
    // Write the entries somewhere
  }
};

class MyStore extends AbstractStore {
  constructor ( id ) {
    super ({
      id,
      backend: MY_BACKEND
    });
  }
}

const store5 = new MyStore ( 'my-store' );

License

MIT © Fabio Spampinato