@pikku/kysely-bun-sqlite 0.12.10 → 0.12.12

package/dist/src/create-bun-sqlite-kysely.d.ts

@@ -1,6 +1,7 @@
 import { Kysely, type KyselyPlugin } from 'kysely';
+import { type TraceDriverOptions } from '@pikku/kysely';
 import type { SqliteFunctionMap } from '@pikku/kysely-sqlite';
-export interface CreateBunSqliteKyselyOptions {
+export interface CreateBunSqliteKyselyOptions extends Omit<TraceDriverOptions, 'system'> {
     /** Path to the SQLite file. Use ':memory:' for an in-memory DB. */
     filename: string;
     /** Apply CamelCasePlugin so DB columns map to camelCase TS fields. Default true. */

package/dist/src/create-bun-sqlite-kysely.js

@@ -1,5 +1,6 @@
 import { Database } from 'bun:sqlite';
 import { Kysely, SqliteDialect, CamelCasePlugin, } from 'kysely';
+import { traceDialect } from '@pikku/kysely';
 import { BunSqliteDatabase } from './bun-sqlite-adapter.js';
 import { registerSqliteFunctions } from './register-functions.js';
 export function createBunSqliteKysely(options) {
@@ -14,7 +15,12 @@ export function createBunSqliteKysely(options) {
     if (options.plugins)
         plugins.push(...options.plugins);
     return new Kysely({
-        dialect: new SqliteDialect({ database: new BunSqliteDatabase(db) }),
+        dialect: traceDialect(new SqliteDialect({ database: new BunSqliteDatabase(db) }), {
+            tracer: options.tracer,
+            currentTrace: options.currentTrace,
+            recordSqlText: options.recordSqlText,
+            system: 'sqlite',
+        }),
         plugins,
     });
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pikku/kysely-bun-sqlite",
-  "version": "0.12.10",
+  "version": "0.12.12",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/pikkujs/pikku.git",
@@ -11,28 +11,33 @@
   "license": "MIT",
   "module": "dist/src/index.js",
   "main": "dist/src/index.js",
+  "files": [
+    "dist",
+    "!dist/**/*.tsbuildinfo"
+  ],
   "type": "module",
   "scripts": {
     "tsc": "tsc",
     "ncu": "npx npm-check-updates",
-    "build": "tsc -b",
+    "build": "bun run clean && tsc -b",
     "test": "bash run-tests.sh",
     "test:coverage": "bash run-tests.sh --coverage",
-    "prepublishOnly": "bun run build"
+    "prepublishOnly": "bun run build",
+    "clean": "rm -rf dist tsconfig.tsbuildinfo"
   },
   "engines": {
     "bun": ">=1.4.0"
   },
   "dependencies": {
-    "@pikku/kysely": "^0.13.18",
-    "@pikku/kysely-sqlite": "^0.12.15",
-    "kysely": "^0.29.5"
+    "@pikku/kysely": "^0.13.43",
+    "@pikku/kysely-sqlite": "^0.12.19",
+    "kysely": "^0.29.6"
   },
   "peerDependencies": {
-    "@pikku/core": "^0.12.124"
+    "@pikku/core": "^0.12.156"
   },
   "devDependencies": {
-    "@pikku/core": "^0.12.124",
-    "@types/bun": "^1.4.0"
+    "@pikku/core": "^0.12.156",
+    "@types/bun": "^1.4.3"
   }
 }

package/CHANGELOG.md

@@ -1,173 +0,0 @@
-# @pikku/kysely-bun-sqlite
-
-## 0.12.10
-
-### Patch Changes
-
-- 1fe79bc: A standalone build of a SQLite app now ships its `db.sqliteExtensions` (sqlite-vec's vec0 by default) inside the artifact, so a migration or query that uses them works in production the way it does under `pikku dev`. The node bundle loads them from `sqlite-extensions/` beside itself; a compiled bun binary embeds them and writes them out under `$PIKKU_DATA_DIR/.pikku-sqlite-extensions/` on start. The libraries are the build machine's, so an extension that cannot be resolved there fails the build; `[]` builds without them.
-
-  `createNodeSqliteKysely` and `createBunSqliteKysely` take an `extensions` list of library paths to load into the connection.
-
-- Updated dependencies [1394385]
-- Updated dependencies [7740547]
-  - @pikku/core@0.12.124
-  - @pikku/kysely-sqlite@0.12.15
-
-## 0.12.9
-
-### Patch Changes
-
-- 1ab831e: Add `openBunSqliteDatabase`, which opens a `bun:sqlite` database as the `SqliteDatabase` Kysely's `SqliteDialect` binds to.
-
-  `createBunSqliteKysely` builds one Kysely over one database, so it cannot express several Kysely instances — differing only in their plugins — sharing a single underlying database. That combination is what lets a plugin-free instance (Better Auth needs unmangled column names) and a CamelCase one address the same tables, and until now an app that needed it had to reach for `better-sqlite3` instead.
-
-  Under Bun that fallback is not survivable: `better-sqlite3` ships a Node-ABI addon which Bun cannot load, and rather than throwing it aborts the process with `NAPI FATAL ERROR: Error::New napi_get_last_error_info`. In a `pikku dev --watch` this killed the dev server after codegen but before it ever listened, with no error naming the driver.
-
-- Updated dependencies [1ab831e]
-  - @pikku/core@0.12.105
-
-## 0.12.8
-
-### Patch Changes
-
-- 6ff72d3: Raise the supported Bun version to 1.4.
-
-  `@pikku/bun-server` and `@pikku/kysely-bun-sqlite` now declare `engines.bun: >=1.4.0`
-  and build against `@types/bun@^1.4.0`. `create-pikku` scaffolds
-  `"packageManager": "bun@1.4.0"`, and the fabric `smoke`/`validate` commands default to
-  and recommend the same version. CI pins `oven-sh/setup-bun` to 1.4.0 instead of
-  tracking `latest`.
-
-## 0.12.7
-
-### Patch Changes
-
-- 746ed6a: fix: one coercion plugin, not three
-
-  The Kysely coercion plugin existed in three copies — the CLI's local database,
-  `@pikku/kysely-node-sqlite` and `@pikku/kysely-bun-sqlite` — and all three had
-  drifted apart. Only the CLI's resolved a column against the tables the query
-  actually named, so two tables that disagree on the kind of a same-named column
-  coerced correctly in local development and silently did not at runtime; only
-  bun's dropped a genuinely ambiguous column instead of letting the last table
-  processed win.
-
-  The single implementation now lives in `@pikku/kysely`, which all three already
-  depended on, and keeps both behaviours: table-qualified resolution first, an
-  ambiguity-safe bare-name fallback second.
-
-  `ColumnKind` — the value type of the generated `coercion.gen.ts` — is
-  `'date' | 'bool' | 'json'`. The CLI's fourth member, `uuid`, was never a
-  coercion kind: the codegen excludes it from the map by construction, because a
-  UUID is a string in both Postgres and SQLite. It is now `AnnotationKind` in the
-  CLI, the union a column may declare in `db/annotations.ts`, of which
-  `ColumnKind` is the coercible subset.
-
-  `@pikku/cli` also drops its unused dependency on the Node-only
-  `@pikku/kysely-node-sqlite`.
-
-- Updated dependencies [5a1a962]
-- Updated dependencies [746ed6a]
-  - @pikku/core@0.12.86
-  - @pikku/kysely@0.13.18
-
-## 0.12.6
-
-### Patch Changes
-
-- 6eef0a0: Bump every dependency to its latest compatible minor/patch across the monorepo.
-- Updated dependencies [7722ceb]
-- Updated dependencies [375c1ff]
-- Updated dependencies [02a70cd]
-- Updated dependencies [aeef159]
-- Updated dependencies [a281de6]
-- Updated dependencies [266e3bc]
-- Updated dependencies [02a70cd]
-- Updated dependencies [786dae5]
-- Updated dependencies [6eef0a0]
-- Updated dependencies [3561d67]
-- Updated dependencies [a91c433]
-- Updated dependencies [02a70cd]
-- Updated dependencies [9537f74]
-- Updated dependencies [2b57ca8]
-- Updated dependencies [266e3bc]
-- Updated dependencies [9fce0f1]
-- Updated dependencies [83683a0]
-- Updated dependencies [456c88b]
-- Updated dependencies [456c88b]
-- Updated dependencies [c127273]
-  - @pikku/core@0.12.85
-  - @pikku/kysely@0.13.17
-  - @pikku/kysely-sqlite@0.12.13
-
-## 0.12.5
-
-### Patch Changes
-
-- 0686513: Declare `@pikku/core` as a peer dependency, matching `@pikku/kysely-sqlite`.
-
-  The package depends on `@pikku/kysely-sqlite`, which requires `@pikku/core` as a
-  peer, but never declared that requirement itself — so an install resolved
-  without complaint and the missing peer only surfaced at runtime. It is now
-  declared the same way its sibling declares it.
-
-- Updated dependencies [7406bfe]
-- Updated dependencies [6794681]
-- Updated dependencies [a7fcd2e]
-  - @pikku/core@0.12.84
-  - @pikku/kysely@0.13.16
-  - @pikku/kysely-sqlite@0.12.12
-
-## 0.12.4
-
-### Patch Changes
-
-- fd9d834: Stop publishing internals that only their own package or file used. The declarations stay; only the entrypoint re-export is removed, so nothing that imported a name from where it is declared is affected.
-- Updated dependencies [fd9d834]
-  - @pikku/kysely@0.13.15
-  - @pikku/kysely-sqlite@0.12.11
-
-## 0.12.3
-
-### Patch Changes
-
-- 9d62571: Make user-defined SQL functions an explicit, checked capability of the SQLite drivers.
-
-  `node:sqlite` can register scalar UDFs (`db.function()`); `bun:sqlite` cannot. Until now
-  neither driver mentioned that, so an app that registered a UDF by reaching for the raw
-  connection worked on Node and, on bun, failed as `no such function: …` from whichever
-  query used it — typically one endpoint breaking in production while everything else
-  looked healthy.
-
-  Both drivers now export `registerSqliteFunctions(db, functions)` and accept a
-  `functions` option on `createNodeSqliteKysely` / `createBunSqliteKysely`. The Node
-  implementation registers them as deterministic; the bun implementation throws
-  `SqliteFunctionsUnsupportedError` — exported from `@pikku/kysely-sqlite`, and naming
-  every function requested — so the incompatibility surfaces at wiring time with a message
-  saying what to do about it.
-
-- Updated dependencies [cabd9dc]
-- Updated dependencies [9d62571]
-  - @pikku/kysely@0.13.8
-  - @pikku/kysely-sqlite@0.12.10
-
-## 0.12.2
-
-### Patch Changes
-
-- 41ce2cb: Upgrade to TypeScript 6 and raise the minimum Node.js version to 22.
-
-  All packages now build against `typescript@^6.0.3` and declare `engines.node >= 22`. Internal tooling (`ts-json-schema-generator`, `zod-to-ts`) was bumped to TypeScript 6-compatible releases.
-
-- Updated dependencies [241e6cf]
-- Updated dependencies [41ce2cb]
-  - @pikku/kysely@0.13.0
-  - @pikku/kysely-sqlite@0.12.7
-
-## 0.12.1
-
-### Patch Changes
-
-- d5c3c85: feat: bun first-class support — new `@pikku/bun-server` runtime and `@pikku/kysely-bun-sqlite` dialect, bun template, CI matrix with `package-manager: [yarn, bun]`, and bun verifier.
-- Updated dependencies [92cd5b1]
-  - @pikku/kysely@0.12.17

package/run-tests.sh

@@ -1,68 +0,0 @@
-#!/bin/bash
-
-# Enable nullglob to handle cases where no files match the pattern
-shopt -s nullglob
-
-# Initialize variables for options
-watch_mode=false
-coverage_mode=false
-
-# Parse command-line options
-while [[ $# -gt 0 ]]; do
-  case $1 in
-    --watch)
-      watch_mode=true
-      shift
-      ;;
-    --coverage)
-      coverage_mode=true
-      shift
-      ;;
-    *)
-      echo "Unknown option: $1"
-      exit 1
-      ;;
-  esac
-done
-
-# Define the pattern to match your test files
-pattern="src/*.test.ts"
-
-# Expand the pattern into an array of files
-files=($(find src -type f -name "*.test.ts"))
-
-# Check if any files matched the pattern
-if [ ${#files[@]} -eq 0 ]; then
-  echo "No test files found matching pattern: $pattern"
-  if [ "${STRICT_TEST_DISCOVERY}" = "1" ]; then
-    exit 1
-  fi
-  exit 0
-fi
-
-# Construct the bun command
-#
-# --parallel gives every test file its own worker process, which is what node's
-# `--test` did. Several suites keep module-level caches (a TypeScript program, a
-# temp fixture directory) that a shared process would leak between files.
-#
-# --timeout because bun caps a test at 5s by default where node had no cap, and
-# the suites that build real TypeScript programs run well past that.
-bun_cmd=(bun test --parallel --timeout 120000)
-
-# Append options based on flags
-if [ "$watch_mode" = true ]; then
-  # --watch reruns in one process; parallel workers have nothing to watch.
-  bun_cmd=(bun test --watch --timeout 120000)
-fi
-
-if [ "$coverage_mode" = true ]; then
-  # --coverage-dir=. keeps lcov.info at the package root: CI merges every
-  # package's report by prefixing its SF paths with the file's own directory,
-  # so a nested coverage/ directory would re-root them one level too deep.
-  bun_cmd+=(--coverage --coverage-reporter=lcov --coverage-reporter=text --coverage-dir=.)
-  export PIKKU_TEST_COVERAGE=1
-fi
-
-# Execute the bun command with the expanded list of files
-"${bun_cmd[@]}" "${files[@]}"