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

@dexto/storage

v1.10.2

Published

Storage backends and config schemas for Dexto agents

Readme

@dexto/storage

Concrete Node storage helpers and config schemas for images that choose to build DextoStores from local backends.

Core (@dexto/core) owns typed domain store contracts such as ConversationStore, SessionStore, MemoryStore, ArtifactStore, and ToolStateStore. This package provides Node backend implementations that image implementations can use internally to compose a DextoStores implementation.

Product layers (CLI/server/apps) can either use these helpers inside an image or provide a native DextoStores implementation directly. Core code should depend on typed stores, not these backend helper classes.

What this package exports

  • Schemas (for config parsing + UI):
    • Import from @dexto/storage/schemas for browser-safe schema-only exports.
  • Concrete implementations (Node runtime):
    • LocalBlobStore, MemoryBlobStore, SQLiteStore, PostgresStore, RedisStore, etc.

Using helpers in an image

import type { DextoImage } from '@dexto/agent-config';
import {
  BackendDextoStores,
  DatabaseBackedArtifactStore,
  DatabaseBackedSessionStore,
  // ...other typed store adapters
} from '@dexto/core/storage';
import {
  StorageSchema,
  LocalBlobStore,
  LocalBlobStoreSchema,
  SQLiteStore,
  SqliteDatabaseSchema,
  MemoryCacheStore,
} from '@dexto/storage';

export const myImage: DextoImage = {
  /* metadata/defaults/tools/hooks/compaction/logger ... */
  storage: {
    configSchema: StorageSchema,
    async createStores(config, logger) {
      const blobStore = new LocalBlobStore(LocalBlobStoreSchema.parse(config.blob), logger);
      const database = new SQLiteStore(SqliteDatabaseSchema.parse(config.database), logger);
      const cache = new MemoryCacheStore();

      return new BackendDextoStores(
        {
          sessions: new DatabaseBackedSessionStore(database, cache),
          artifacts: new DatabaseBackedArtifactStore(blobStore),
          // ...provide every DextoStoreMap domain
        },
        {
          async connect() {
            await cache.connect();
            await database.connect();
            await blobStore.connect();
          },
          async disconnect() {
            await Promise.all([cache.disconnect(), database.disconnect(), blobStore.disconnect()]);
          },
          isConnected() {
            return cache.isConnected() && database.isConnected() && blobStore.isConnected();
          },
        },
      );
    },
  },
};

Schemas and .passthrough()

Agent config parsing needs to accept custom backends with provider-specific fields, so the top-level storage config schemas are envelopes that validate only the discriminator:

storage:
  blob:
    type: local
    storePath: ./data/blobs
  database:
    type: sqlite
    path: ./data/agent.db
  cache:
    type: in-memory

Those envelope schemas use .passthrough() so extra fields survive initial parsing. Detailed validation happens later inside the loaded image's storage.createStores(...) implementation.