🔧 update: migrate to node.js runtime with bun as toolchain

[warengonzaga]

Summary

Migrates the runtime from a Bun-first dual-adapter approach to a pure Node.js runtime while keeping Bun as the build/test toolchain. This widens compatibility to any Node.js >=22 environment without requiring Bun at runtime.

Motivation

The Bun-first design required consumers to either run Bun or carry bundling workarounds. Node.js has significantly broader ecosystem support, making config-engine usable in any standard Node.js project without runtime-specific conditions.

Changes

Runtime (src/runtime.ts)

• Remove isBun() detection and the entire openBunDatabase() / getBunSqliteSpecifier() path
• Simplify openDatabase() to always use better-sqlite3

Dependencies (package.json)

• Drop @types/bun devDependency, add @types/better-sqlite3
• Make better-sqlite3 a required peer dependency (remove optional flag)
• Update engines to ^22.0.0 || ^24.0.0 || ^26.0.0 (matches CI matrix, aligns with org standard)
• Add packageManager: bun@1.3.9
• Update description and keywords to reflect Node.js runtime

Build (scripts/build.ts, tsconfig.json)

• Remove bun:sqlite from build externals
• Remove types: ["bun"] from tsconfig compilerOptions

CI (.github/workflows/build-flow.yml)

• Migrate from package-build-flow-action to build-flow-action/app.yml@v0.2.0 (org-standard reusable workflow)
• Rename build.yml → build-flow.yml to match org convention
• Use ci-profile: node-bun with matrix ["22", "24", "26"] — tests Node 22 LTS, 24 current, 26 latest
• Enable package publishing to both NPM and GitHub Packages (enable-package: true, package-registry: both)
• Add concurrency group and workflow_dispatch trigger

Tests (tests/runtime.test.ts)

• Simplify bundle regression test: verifies no bun:sqlite leakage and that better-sqlite3 stays external

Docs / misc

• Update module-level JSDoc in src/index.ts
• Update src/types.ts adapter comment
• Fix src/encryption.ts install hint (bun add → npm install)

[Copilot]

Pull request overview

Migrates config-engine to a Node.js-only runtime by removing Bun runtime branching and standardizing the SQLite adapter on better-sqlite3, while continuing to use Bun for build/test tooling. This aligns the package with Node.js >=22 environments without requiring Bun at runtime.

Changes:

• Simplify runtime DB adapter to always use better-sqlite3 and remove Bun runtime detection.
• Update dependencies/engines to reflect Node.js runtime support and better-sqlite3 as a required peer dependency.
• Adjust build/test/tooling configs to remove Bun runtime typing and prevent Bun-specific SQLite leakage in node-targeted bundles.

Reviewed changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
tsconfig.json	Removes Bun type injection to reflect Node.js-targeted runtime compilation.
tests/runtime.test.ts	Updates bundle regression test to check for Bun-specific imports and better-sqlite3 externalization.
src/types.ts	Updates adapter interface documentation to match the single-driver runtime.
src/runtime.ts	Removes Bun runtime path and standardizes DB open logic on better-sqlite3.
src/index.ts	Updates module-level docs to describe Node.js runtime + Bun toolchain.
src/encryption.ts	Updates peer dependency install hint to npm to match Node.js consumer runtime.
scripts/build.ts	Removes bun:sqlite from externals since it’s no longer a runtime concern.
package.json	Updates description/keywords/engines; swaps Bun types for @types/better-sqlite3; makes better-sqlite3 a required peer dep.
.github/workflows/build.yml	Bumps CI Node version to 22 to match the new engines/runtime target.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.