Spun out of the anchored-chain packaging PR. @bounded-systems/anchored-chain-sqlite cannot produce a runnable Node JS bundle: it imports bun:sqlite, drizzle-orm/bun-sqlite, and uses Bun's import ... with { type: 'text' } / { type: 'json' } attributes for the bundled .sql/.json migrations. None survive a plain tsc→JS Node build.
Current decision (implemented in the PR): ship it Bun-only —
exports: bun→./src/index.ts, default→./src/index.ts (source is the runtime entry), types→./dist/index.d.ts.
dist is declaration-only (emitDeclarationOnly), just for editor/type consumers.
engines.bun declared.
Open questions to confirm before/at extraction
Context: claude.ai/code session 01PGAut6CEjiQjFMURp8UA5A
Spun out of the anchored-chain packaging PR.
@bounded-systems/anchored-chain-sqlitecannot produce a runnable Node JS bundle: it importsbun:sqlite,drizzle-orm/bun-sqlite, and uses Bun'simport ... with { type: 'text' }/{ type: 'json' }attributes for the bundled.sql/.jsonmigrations. None survive a plaintsc→JS Node build.Current decision (implemented in the PR): ship it Bun-only —
exports:bun→./src/index.ts,default→./src/index.ts(source is the runtime entry),types→./dist/index.d.ts.distis declaration-only (emitDeclarationOnly), just for editor/type consumers.engines.bundeclared.Open questions to confirm before/at extraction
require/importthis under Node? (If so, we'd need a portable sqlite driver + a real JS build — a larger change.)drizzle-ormbe apeerDependencyrather than a directdependency, to avoid version pinning across consumers?src/migrations/**) resolve correctly from the published package when loaded under thebuncondition (they ship viafiles, but worth an install-and-run smoke test).Context: claude.ai/code session 01PGAut6CEjiQjFMURp8UA5A