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

@zapo-js/store-mongo

v1.0.2

Published

MongoDB store provider for zapo-js

Readme

@zapo-js/store-mongo

MongoDB-backed persistent store for zapo-js. Good fit for fleets that already operate on MongoDB and want session state to ride that same infrastructure (replica sets, Atlas, etc.).

Cache domains are backed by MongoDB TTL indexes - expired documents are pruned by the server's TTL monitor (~60s sweep), so no background cleanup job is required from your side.

Install

npm install @zapo-js/store-mongo mongodb

mongodb is a peer dependency.

Quick start

import { createStore, WaClient } from 'zapo-js'
import { createMongoStore } from '@zapo-js/store-mongo'

const store = createStore({
    backends: {
        mongo: createMongoStore({
            db: { uri: 'mongodb://localhost:27017', database: 'wa' },
            collectionPrefix: 'wa_'
        })
    },
    providers: {
        auth: 'mongo',
        signal: 'mongo',
        senderKey: 'mongo',
        appState: 'mongo',
        privacyToken: 'mongo'
    }
})

const client = new WaClient({ store, sessionId: 'default' })

Config

createMongoStore(config) accepts:

| Field | Description | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | db | Existing Db or { uri, database, options? } to build a new client. When the store builds the client itself, destroy() will close() it for you. | | collectionPrefix | Prepended to every collection name. | | cacheTtlMs | TTLs for retry, groupMetadata, deviceList, messageSecret (TTL indexes). |

The result exposes { db, stores, caches, destroy } so you can reuse the database handle and shut the client down cleanly on exit.

Notes

  • Pass an externally-owned Db when you want full control over the connection (replica sets, Atlas pooling, transactions across apps).
  • The TTL-monitor latency means cache entries can outlive the TTL by up to ~1 minute. Acceptable for groupMetadata/deviceList; for tighter eviction prefer @zapo-js/store-redis.
  • Indexes are created lazily on first touch per collection (one-time cost). Subsequent process restarts skip the create step.

See the main zapo-js docs for the full store contract.