@pikku/kysely-node-sqlite 0.12.9 → 0.12.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pikku/kysely-node-sqlite",
-  "version": "0.12.9",
+  "version": "0.12.10",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/pikkujs/pikku.git",
@@ -15,29 +15,35 @@
   "scripts": {
     "tsc": "tsc",
     "ncu": "npx npm-check-updates",
-    "build": "tsc -b",
+    "build": "bun run clean && tsc -b",
     "test": "bash run-tests.sh",
     "test:watch": "bash run-tests.sh --watch",
     "test:coverage": "bash run-tests.sh --coverage",
-    "prepublishOnly": "bun run build"
+    "prepublishOnly": "bun run build",
+    "clean": "rm -rf dist tsconfig.tsbuildinfo"
   },
   "engines": {
     "node": ">=22.10"
   },
   "dependencies": {
-    "@pikku/kysely": "^0.13.25",
-    "@pikku/kysely-sqlite": "^0.12.15",
-    "kysely": "^0.29.5"
+    "@pikku/kysely": "^0.13.39",
+    "@pikku/kysely-sqlite": "^0.12.18",
+    "kysely": "^0.29.6"
   },
   "peerDependencies": {
-    "@pikku/core": "^0.12.124"
+    "@pikku/core": "^0.12.144"
   },
   "devDependencies": {
-    "@pikku/core": "^0.12.124",
-    "@types/node": "^22",
-    "tsx": "^4.23.12"
+    "@pikku/core": "^0.12.144",
+    "@types/node": "^26",
+    "tsx": "^4.23.15"
   },
   "exports": {
-    ".": "./dist/src/index.js"
-  }
+    ".": "./dist/src/index.js",
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "dist",
+    "!dist/**/*.tsbuildinfo"
+  ]
 }

package/CHANGELOG.md

@@ -1,200 +0,0 @@
-# @pikku/kysely-node-sqlite
-
-## 0.12.9
-
-### 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.8
-
-### Patch Changes
-
-- 4c7a1b5: Run the monorepo's own scripts through bun instead of yarn. What moves is the
-  package manager each package's `prepublishOnly` and build scripts invoke, plus
-  the two manifest fixes bun needs to resolve the tree: `uWebSockets.js` is
-  declared with an explicit `github:` specifier, and `@pikku/uws-handler` marks
-  its `uWebSockets.js` peer optional so a bun install of a consumer that brings
-  its own uWS app does not try to fetch it from the registry.
-
-  Three published behaviours change, all of them cases where an isolated
-  `node_modules` or bun as the runtime had been papered over by yarn's hoisting:
-
-  - `@pikku/migrator-sql` turns foreign keys on when it opens a sqlite database
-    through bun. `node:sqlite` enforces them by default and `bun:sqlite` does not,
-    which silently turned every `ON DELETE CASCADE` into a no-op under
-    `bunx --bun pikku`.
-  - `@pikku/cli` resolves a deploy provider against the project being deployed
-    rather than against wherever the CLI itself is installed, which is what its
-    own "is not installed" error asks the user to arrange.
-  - `@pikku/cli` treats a specifier a runtime hands straight back — bun does this
-    for the modules it implements itself — as not resolved from the project, so
-    it falls back rather than loading the runtime's own copy.
-
-- Updated dependencies [4c7a1b5]
-  - @pikku/core@0.12.108
-  - @pikku/kysely@0.13.25
-  - @pikku/kysely-sqlite@0.12.14
-
-## 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
-
-- 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 [063f43a]
-- Updated dependencies [ce66bf8]
-- Updated dependencies [d0307a8]
-- Updated dependencies [ce66bf8]
-- Updated dependencies [3ad2131]
-- Updated dependencies [b930dca]
-- Updated dependencies [b95e77d]
-- Updated dependencies [fd9d834]
-- Updated dependencies [8978fbd]
-  - @pikku/core@0.12.82
-  - @pikku/kysely@0.13.15
-  - @pikku/kysely-sqlite@0.12.11
-
-## 0.12.4
-
-### 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 [32277d5]
-- Updated dependencies [ea8aabf]
-- Updated dependencies [33e96ab]
-- Updated dependencies [fd72e58]
-- Updated dependencies [cabd9dc]
-- Updated dependencies [fd72e58]
-- Updated dependencies [fd72e58]
-- Updated dependencies [894b2f8]
-- Updated dependencies [dd19aa7]
-- Updated dependencies [50ec500]
-- Updated dependencies [9d62571]
-  - @pikku/core@0.12.75
-  - @pikku/kysely@0.13.8
-  - @pikku/kysely-sqlite@0.12.10
-
-## 0.12.3
-
-### 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/core@0.12.44
-  - @pikku/kysely-sqlite@0.12.7
-
-## 0.12.2
-
-### Patch Changes
-
-- 34f254e: Bump the `kysely` dependency range to `^0.29.0` so it dedupes onto a single
-  copy alongside Better Auth (which bundles kysely 0.29.x), avoiding two
-  incompatible `Kysely` classes (the `#private` brand mismatch) when both pikku's
-  adapters and Better Auth share a database connection.
-
-  kysely 0.29 is ESM-only, which the unmaintained `kysely-plugin-serialize`
-  (no `exports` map, CommonJS build) cannot import. Its `SerializePlugin` is now
-  maintained directly in `@pikku/kysely` and re-exported, and the external
-  dependency is dropped from `@pikku/kysely`, `@pikku/kysely-sqlite`, and
-  `@pikku/cloudflare`.
-
-- Updated dependencies [6565b97]
-- Updated dependencies [34f254e]
-  - @pikku/kysely@0.12.16
-  - @pikku/kysely-sqlite@0.12.6
-
-## 0.12.1
-
-### Patch Changes
-
-- 9060165: New `@pikku/kysely-node-sqlite` provides a Kysely dialect and migrator for Node's built-in `node:sqlite`. `@pikku/kysely-sqlite` adds a `LibsqlWebDialect` for running Kysely against Cloudflare Workers and Turso databases over HTTP.
-- Updated dependencies [9060165]
-  - @pikku/kysely-sqlite@0.12.5

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[@]}"