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

@tussle/storage-pool

v0.7.10

Published

Tussle storage which pools multiple tussle storage services

Readme

Tussle Storage Pool

Pool multiple Tussle storage services into a single logical storage service with smart-switching behavior.

When attempting to create a new file upload, each store is tried until success. The pool will then attempt to direct all subsequent operations to the sub-storage in which the upload was initially created.

At this time, there is no support for splitting a file upload across multiple sub-stores so the 'concatenation' extension is unsupported. This capability may be added in the future (PRs welcome!).

TussleStoragePool is compatible with transient state providers (StateMemory, StateMemoryTTL). As long as the pool is constructed with the same configuration, then pool state will be reconstructed from the sub-stores as needed.

Configuration

import {TussleStoragePool} from '@tussle/storage-pool';
import {TussleStorageR2} from '@tussle/storage-r2';
import {TussleStateMemoryTTL} from '@tussle/state-memory-ttl';

const r2Primary = new TussleStorageR2({
  stateService: new TussleStateMemoryTTL(),
  bucket: R2_BUCKET_PRIMARY,
});

const r2Failover = new TussleStorageR2({
  stateService: new TussleStateMemoryTTL(),
  bucket: R2_BUCKET_FAILOVER,
});

const storage = new TussleStoragePool({
  stateService: new TussleStateMemoryTTL(),
  stores: {
    'primary': r2Primary,
    'failover': r2Failover,
  },
});

Methods

While TussleStoragePool implements all the TussleStorageService methods, they also take an optional storageKey parameter which should correspond to the names defined in the pool's stores object. Similarly, response bodies will always include an additional storageKey: string indicating which sub-store handled the request.

Providing a storageKey for createFile() is all that's necessary to permanently route operations for the created file to the same storage service.

Calling getFileInfo() for a location will scan the pool for a match if there is no location-to-store mapping cached in the pool. If a match is found, then the location-to-store mapping is cached within the TussleStoragePool for subsequent operations.