Alexandro.Net

Download README · GitHub release

ai-memory-sqlite

Unscoped convenience entry point for Stackline AI SQLite conversation memory.

npm version license GitHub repository Docs Reddit community

Documentation | npm | Issues | Repository

Current package version: 0.0.4


Why this package?

Unscoped convenience entry point for @stackline/ai-memory-sqlite. It re-exports the canonical package's runtime and TypeScript API without adding behavior. The source now lives alongside the scoped package so their dependency versions and GitHub Actions publication can be checked together.

Compatibility

Item Value
Package ai-memory-sqlite@0.0.4
Supported Node.js >=18.17.0
Module entry index.js (ES modules)
Types index.d.ts
Canonical dependency @stackline/ai-memory-sqlite@0.0.4

The canonical adapter's backend requirements, options, and limitations also apply to this entry point.

Installation

npm install ai-memory-sqlite

Usage

import { createSqliteMemoryStore } from "ai-memory-sqlite";

Use the same arguments and return values as the canonical adapter.

Security

This entry point shares its implementation and security boundaries with @stackline/ai-memory-sqlite. Keep provider credentials, database access, and memory paths on the backend. Follow the security policy when reporting vulnerabilities.

API Surface

Every named runtime export and TypeScript declaration is re-exported from @stackline/ai-memory-sqlite. The canonical README contains the complete examples, configuration, error behavior, and limitations.

Local Development

Clone the monorepo and run from its root with the Node and pnpm versions declared there:

pnpm install --frozen-lockfile
pnpm run check

Consumer Smoke Test

pnpm run pack:release
node scripts/consumer-smoke.mjs release-artifacts

The consumer installs the scoped packages and aliases together, verifies that alias runtime exports have the same identities, and compiles the alias TypeScript imports.

Release Checklist

  1. Keep the alias re-exports and scoped dependency aligned with the corresponding workspace package.
  2. Run the workspace checks, full and production dependency audits, and consumer smoke test.
  3. Publish through publish.yml, verifying the expected_manifest_sha512 input against the reviewed archive manifest.
  4. Publish scoped dependencies before aliases and verify public npm bytes and provenance.

License

MIT. Copyright notices are retained from the canonical Stackline package.

Credits and original authors

Original copyright, license notices and contributor acknowledgements remain part of this distribution. Stackline maintenance does not replace authorship of the original work.

Community and Links

Use this repository's issue tracker for reproducible bugs and feature requests. Join r/Stackline for examples, usage questions and release discussions.