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

@owservable/sqlite

v3.1.0

Published

owservable sqlite backend adapter: journal-trigger live updates, MikroORM entities and process entities

Readme

owservable

@owservable/sqlite

📖 API Docs · ✅ Coverage

SQLite backend adapter for @owservable/core: live data via journal-table triggers over MikroORM entities — including changes made by other processes writing to the same database file.

Built for scenarios like a live UI over a SQLite file that backend processes (e.g. mastra.ai agents and workflows) write to, desktop/electron tools, and local-first apps.

🚀 Features

  • SqliteBackend: implements IObservableBackend over a MikroORM entity — change feed, queries with Mongo-style operators, relation population
  • Journal-table change capture: installSqliteTriggers attaches AFTER INSERT/UPDATE/DELETE triggers writing to a _owservable_changes journal — SQLite triggers fire regardless of which connection or process writes, so external writers are fully visible
  • SqliteJournalPoller: reads the journal on a short interval (default 250 ms, an indexed range scan on a usually-empty table), emits normalized change events, prunes consumed rows
  • Changed-column tracking: the update trigger records exactly which columns changed (generated per-column comparisons), so stores keep their field-intersection reload optimizations
  • SqliteObservableTable: PK-refetch enrichment and column→property mapping — change events are shaped exactly like MongoDB change streams
  • updateSchema: false mode: map entities over tables owned by another tool (e.g. mastra's storage schema) — the connector attaches triggers and registers backends without touching DDL
  • SqliteConnector: MikroORM init, WAL + busy_timeout pragmas, optional updateSchema({safe: true}), trigger install, poller and backend registration in one call

📦 Installation

npm install @owservable/core @owservable/sqlite @mikro-orm/core @mikro-orm/sqlite

or

pnpm add @owservable/core @owservable/sqlite @mikro-orm/core @mikro-orm/sqlite

⚠️ Operational requirements

  • WAL mode is set automatically and is mandatory for the multi-process case (external writer + owservable reader on the same file)
  • Local file databases only — remote libsql (Turso/sqld) has no shared file to watch
  • Update latency equals the poll interval (default 250 ms)
  • Triggers on externally-owned tables are additive and safe, but external migrations that drop/recreate tables remove them — the idempotent bootstrap re-installs on every boot

📄 License

Unlicense — see LICENSE.