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

@chatcops/store-sqlite

v0.3.0

Published

SQLite storage for ChatCops single-server deployments

Readme

@chatcops/store-sqlite

SQLite storage for ChatCops single-server deployments. It uses Node.js 22.13+'s built-in node:sqlite, so no native database dependency is required.

Node may print an ExperimentalWarning the first time node:sqlite loads; this is expected from Node and is not an error.

pnpm add @chatcops/store-sqlite
import express from 'express';
import { chatcopsMiddleware } from '@chatcops/server';
import { sqliteStorage } from '@chatcops/store-sqlite';

const storage = sqliteStorage({ path: './chatcops.db' });

const app = express();
app.use(express.json());
app.use('/api/chat', chatcopsMiddleware({
  provider: { type: 'claude', apiKey: process.env.ANTHROPIC_API_KEY! },
  systemPrompt: 'You are a helpful assistant.',
  sessionSecrets: [process.env.CHATCOPS_SESSION_SECRET!],
  storage,
}));

Use path: ':memory:' for tests, or pass an already-open node:sqlite DatabaseSync (or structurally compatible better-sqlite3 database) with database.

SQLite is intended here for one server process and a local file. Back up the database file using your normal deployment process. Call await storage.close?.() during graceful shutdown.

Extra columns

To stamp columns of your own (a tenant or site id) on every new row, add them with your own ALTER TABLE and pass extraColumns with a rowHook:

import { DatabaseSync } from 'node:sqlite';
import { sqliteStorage } from '@chatcops/store-sqlite';

const database = new DatabaseSync('./chatcops.db');
database.exec('ALTER TABLE chatcops_conversations ADD COLUMN workspace_id TEXT');
database.exec('ALTER TABLE chatcops_messages ADD COLUMN workspace_id TEXT');

const storage = sqliteStorage({
  database,
  extraColumns: ['workspace_id'],
  rowHook: ({ metadata }) => ({ workspace_id: metadata?.workspaceId }),
});

The hook runs when a row is created, never on updates. It gets the table, the conversation id, the metadata passed with the write, and the message for message rows. Returning a key that isn't in extraColumns throws and nothing from that write is stored. Values are bound as parameters, never put into the SQL, and must be strings, numbers, booleans (stored as 1 or 0) or null.

The { workspace_id: 'uuid' } form from @chatcops/store-postgres works too, so one config fits both stores. SQLite ignores the type.