Plugin fails to load on v2.14.3: `require("bun:sqlite")` in ESM scope in `sqlite-bootstrap.js`

[leiverkus]

Summary

Sister bug to #112 (closed in 2.14.3). The JSON-import-attribute issue is fixed, but a second strict-ESM violation in dist/services/sqlite/sqlite-bootstrap.js keeps the plugin from loading on opencode ≥1.15 (Bun-based runtime).

Error

opencode log:

ERROR service=plugin path=opencode-mem
  target=file:///…/opencode-mem@latest/node_modules/opencode-mem/dist/plugin.js
  error=require is not defined in ES module scope, you can use import instead
  in dist/services/sqlite/sqlite-bootstrap.js:4
    const bunSqlite = require("bun:sqlite");
failed to load plugin

Root Cause

src/services/sqlite/sqlite-bootstrap.ts mixes a CommonJS require() call into an ESM module (parent package.json has "type": "module"):

let Database: typeof import("bun:sqlite").Database;

export function getDatabase(): typeof import("bun:sqlite").Database {
  if (!Database) {
    const bunSqlite = require("bun:sqlite") as typeof import("bun:sqlite");
    Database = bunSqlite.Database;
  }
  return Database;
}

Under Bun's strict-ESM mode (used by opencode's embedded Bun runtime in 1.15.x), require is not available in ESM scope. The compiled dist/services/sqlite/sqlite-bootstrap.js carries the same require() call verbatim.

Fix

One-line change — replace require() with a top-level static import (which works fine because bun:sqlite is a Bun built-in):

import { Database as BunDatabase } from "bun:sqlite";

let Database: typeof BunDatabase;
export function getDatabase(): typeof BunDatabase {
  if (!Database) Database = BunDatabase;
  return Database;
}

I verified the workaround locally by overwriting the cached dist/services/sqlite/sqlite-bootstrap.js with the equivalent ESM-only version — plugin now loads cleanly on opencode 1.15.10 / Bun-v1.3.14 / macOS arm64.

Environment

• macOS 26.3 (Apple Silicon, arm64)
• opencode 1.15.10 (Homebrew anomalyco/opencode, embeds bun-v1.3.14)
• opencode-mem 2.14.3 (latest), installed via opencode's plugin cache at ~/.cache/opencode/packages/opencode-mem@latest/

Related

• Same flavor as Plugin fails to load on opencode ≥1.15: import pkg from "../package.json" needs with { type: "json" } (regression in 2.14.0) #112 (JSON-import-attribute), closed in v2.14.3 — this is the leftover sibling in the same area.

[leiverkus]

Update — applied my own patch, hit a deeper issue

After overwriting the cached dist/services/sqlite/sqlite-bootstrap.js with the ESM-correct version (import { Database as BunDatabase } from "bun:sqlite" instead of require("bun:sqlite")), the plugin moved one step further but failed with:

ERROR service=plugin path=opencode-mem
  target=file:///…/opencode-mem@latest/node_modules/opencode-mem/dist/plugin.js
  error=Only URLs with a scheme in: file, data, node, and electron are
        supported by the default ESM loader. Received protocol 'bun:'
  failed to load plugin

That error wording is Node's internal/modules/esm/loader.js verbatim — file/data/node/electron is Node's standard allowed-scheme list. I confirmed the opencode binary (1.15.10, Homebrew anomalyco/opencode) embeds Node's ESM resolver: strings $(which opencode) | grep "default ESM loader" matches Node deprecation messages directly. The Bun runtime that's bundled (bun-v1.3.14) is apparently used for other purposes; the plugin loader is Node.

So the require("bun:sqlite") fix is necessary (the file is malformed ESM) but not sufficient — opencode-mem fundamentally cannot load on a Node-based plugin loader because bun:sqlite is a Bun built-in with no Node equivalent.

Suggested direction

Probably the plugin needs to support both runtimes, e.g. detect at startup and fall back to better-sqlite3 when bun:sqlite isn't available:

let DatabaseCtor;
try {
  ({ Database: DatabaseCtor } = await import("bun:sqlite"));
} catch {
  ({ default: DatabaseCtor } = await import("better-sqlite3"));
}

This would parallel how the plugin already does graceful fallback for USearch → ExactScan. Without this, the plugin won't load on anomalyco/opencode 1.15.x (and likely the official sst-cli/opencode too — its Homebrew formula lists node as a required runtime dependency).

The one-line require → import fix in the OP is still correct and worth shipping — it just isn't the whole story. Filing this as an addendum rather than closing because the title still accurately describes the first symptom you hit.