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

bedrock-web-store

v1.2.2

Published

Shared storage for Bedrock Web Apps

Downloads

41

Readme

bedrock-web-store

A module for creating shared storage for Bedrock Web Apps. The design requires stored objects to have only one instance in memory. The objects may be backed by a persistent storage layer such as localStorage or IndexedDB. Whether or not persistent storage is used is determined by the underlying engine associated with a particular Store instance.

It is important to note that even if a persistent storage mechanism is used, any objects retrieved from storage via the Store API will have only one in-memory copy, ensuring that frontend components will share the same instance. That is to say that a naive implementation of a Store engine that simply maps the API onto, for example, localForage or localStorage would break this guarantee. There must also be a shared memory layer.

Usage

npm install bedrock-web-store

Simple default singleton storage

The most common setup for a Web App is to use a single instance of shared storage across the application. Namespacing can be achieved via the id parameter.

In setup file:

import {store, MemoryEngine} from 'bedrock-web-store';

store.setEngine({engine: new MemoryEngine()});

In file 1:

import {store} from 'bedrock-web-store';

const foo = {a: 1, b: 2};

store.create({id: '123', object: foo});

In file 2:

import {store} from 'bedrock-web-store';

const foo = store.get({id: '123'});

console.log(foo.a);
// yields "1"

Multiple stores

More complex Web Apps may have a reason for partitioning storage into different instances. This could be done for namespacing purposes where ids would otherwise clash or because different storage engines are needed for different purposes. In this case, the Store class can be imported and multiple instances (potentially with different engines) can be created and managed by the Web App.

In custom myStores.js:

import {Store, MemoryEngine} from 'bedrock-web-store';

export const stores = {};

stores.foos = new Store({engine: new MemoryEngine()});
stores.bars = new Store({engine: new MemoryEngine()});

In file 1:

import {stores} from './myStores.js';

const foo = {a: 1, b: 2};
stores.foos.create({id: '123', object: foo});

// ...

In file 2:

import {stores} from './myStores.js';

const foo = stores.foos.get({id: '123'});
// same `foo` as file 1

// ...

const bar = stores.bars.get({id: '123'});
// `bar` is undefined