dbgate-sqlite-dumper 0.1.0 → 0.1.1

package/docs/supported-data-types.md

@@ -1,74 +1,74 @@
-# Supported data types
-
-SQLite stores every value in one of five storage classes, whatever a column is declared
-as. A dump writes each value according to its storage class, exactly as the native `.dump`
-writes it — and restoring it yields the same storage class and the same value.
-
-| Storage class | Written as                                    | Example                                  |
-| ------------- | --------------------------------------------- | ---------------------------------------- |
-| `NULL`        | `NULL`                                        | `NULL`                                   |
-| `INTEGER`     | decimal                                       | `9223372036854775807`                    |
-| `REAL`        | `%lld.0` when integral, else `%!.20g`         | `3.0`, `0.100000000000000005`, `1.0e+20` |
-|               | infinities                                    | `9.0e+999`, `-9.0e+999`                  |
-| `TEXT`        | quoted, `'` doubled, newlines via `replace()` | `replace('a\nb','\n',char(10))`          |
-| `BLOB`        | lower-case hex                                | `X'00ff'`, `X''`                         |
-
-## How values are read
-
-Row data never passes through a JavaScript number, and text never passes through the
-driver's decoder. The `SELECT` that reads a table has SQLite itself produce, per column:
-
-- `INTEGER` → `CAST(x AS TEXT)`: exact at 64 bits, whatever the driver would have done;
-- `REAL` → the literal, computed in SQL with the shell's own rule — including SQLite's
-  `printf('%!.20g')`, so the digits are the ones SQLite writes, which no JavaScript number
-  formatting reproduces;
-- `TEXT` → `CAST(x AS BLOB)`: the stored bytes (in a UTF-16 database, the text itself);
-- `BLOB` → the bytes.
-
-## Notes per class
-
-### `INTEGER`
-
-Exact across the full 64-bit range. `AUTOINCREMENT` counters are read as text too, so a
-counter past 2^53 resumes at exactly the right value.
-
-### `REAL`
-
-The literal round-trips to the identical double: `%!.20g` carries more than the 17
-significant digits that identify one. The digits beyond the 17th vary between SQLite
-releases (see [native-compatibility.md](native-compatibility.md#the-one-exception-real-digit-tails)),
-never the value.
-
-A `REAL` holding an integral value is written with `.0` (`3.0`), so it is restored as a
-`REAL`, not an `INTEGER`. `-0.0` is written as `0.0`, as natively.
-
-### `TEXT`
-
-- **Quoting:** the only escape SQLite has is a doubled `'`. There are no backslash escapes.
-- **Newlines and carriage returns** are written as `replace('…\n…','\n',char(10))` (and
-  `char(13)`), with a placeholder that does not otherwise occur in the text — so each
-  `INSERT` stays on one line and survives tools that rewrite line endings. With
-  `dataExport.rawNewlines` (native `--newlines`) they are written raw instead.
-- **Bytes that are not valid UTF-8** — SQLite does not validate what it stores — are
-  written raw, as natively, so the dump reproduces the stored value exactly. Such a dump is
-  not valid UTF-8, which is why the writer and the restore handle bytes. On restore through
-  a JavaScript driver, such a literal is executed as `CAST(X'…' AS TEXT)`, the identical
-  bytes.
-- **`NUL` characters** are kept, written as `'a'||char(0)||'b'`. The native shell truncates
-  text at the first `NUL`; this is the one place this package writes something the shell
-  would not, and only for text the shell cannot represent.
-
-### `BLOB`
-
-Always hex. An empty blob is `X''`, distinct from `NULL` and from the empty string `''`.
-
-## Declared types
-
-A column's declared type — `VARCHAR(20)`, `DATETIME`, `BOOLEAN`, `JSON`, or none at all —
-is part of the table's DDL and is reproduced verbatim. It only determines the column's
-_affinity_, which SQLite applies on insert; since every value is written in the storage
-class it already has, affinity cannot change it on restore. `STRICT` tables are restored as
-`STRICT`, with their type checks.
-
-Dates and times have no storage class of their own in SQLite; they are whatever text,
-number or blob the application stored, and are dumped as such.
+# Supported data types
+
+SQLite stores every value in one of five storage classes, whatever a column is declared
+as. A dump writes each value according to its storage class, exactly as the native `.dump`
+writes it — and restoring it yields the same storage class and the same value.
+
+| Storage class | Written as                                    | Example                                  |
+| ------------- | --------------------------------------------- | ---------------------------------------- |
+| `NULL`        | `NULL`                                        | `NULL`                                   |
+| `INTEGER`     | decimal                                       | `9223372036854775807`                    |
+| `REAL`        | `%lld.0` when integral, else `%!.20g`         | `3.0`, `0.100000000000000005`, `1.0e+20` |
+|               | infinities                                    | `9.0e+999`, `-9.0e+999`                  |
+| `TEXT`        | quoted, `'` doubled, newlines via `replace()` | `replace('a\nb','\n',char(10))`          |
+| `BLOB`        | lower-case hex                                | `X'00ff'`, `X''`                         |
+
+## How values are read
+
+Row data never passes through a JavaScript number, and text never passes through the
+driver's decoder. The `SELECT` that reads a table has SQLite itself produce, per column:
+
+- `INTEGER` → `CAST(x AS TEXT)`: exact at 64 bits, whatever the driver would have done;
+- `REAL` → the literal, computed in SQL with the shell's own rule — including SQLite's
+  `printf('%!.20g')`, so the digits are the ones SQLite writes, which no JavaScript number
+  formatting reproduces;
+- `TEXT` → `CAST(x AS BLOB)`: the stored bytes (in a UTF-16 database, the text itself);
+- `BLOB` → the bytes.
+
+## Notes per class
+
+### `INTEGER`
+
+Exact across the full 64-bit range. `AUTOINCREMENT` counters are read as text too, so a
+counter past 2^53 resumes at exactly the right value.
+
+### `REAL`
+
+The literal round-trips to the identical double: `%!.20g` carries more than the 17
+significant digits that identify one. The digits beyond the 17th vary between SQLite
+releases (see [native-compatibility.md](native-compatibility.md#the-one-exception-real-digit-tails)),
+never the value.
+
+A `REAL` holding an integral value is written with `.0` (`3.0`), so it is restored as a
+`REAL`, not an `INTEGER`. `-0.0` is written as `0.0`, as natively.
+
+### `TEXT`
+
+- **Quoting:** the only escape SQLite has is a doubled `'`. There are no backslash escapes.
+- **Newlines and carriage returns** are written as `replace('…\n…','\n',char(10))` (and
+  `char(13)`), with a placeholder that does not otherwise occur in the text — so each
+  `INSERT` stays on one line and survives tools that rewrite line endings. With
+  `dataExport.rawNewlines` (native `--newlines`) they are written raw instead.
+- **Bytes that are not valid UTF-8** — SQLite does not validate what it stores — are
+  written raw, as natively, so the dump reproduces the stored value exactly. Such a dump is
+  not valid UTF-8, which is why the writer and the restore handle bytes. On restore through
+  a JavaScript driver, such a literal is executed as `CAST(X'…' AS TEXT)`, the identical
+  bytes.
+- **`NUL` characters** are kept, written as `'a'||char(0)||'b'`. The native shell truncates
+  text at the first `NUL`; this is the one place this package writes something the shell
+  would not, and only for text the shell cannot represent.
+
+### `BLOB`
+
+Always hex. An empty blob is `X''`, distinct from `NULL` and from the empty string `''`.
+
+## Declared types
+
+A column's declared type — `VARCHAR(20)`, `DATETIME`, `BOOLEAN`, `JSON`, or none at all —
+is part of the table's DDL and is reproduced verbatim. It only determines the column's
+_affinity_, which SQLite applies on insert; since every value is written in the storage
+class it already has, affinity cannot change it on restore. `STRICT` tables are restored as
+`STRICT`, with their type checks.
+
+Dates and times have no storage class of their own in SQLite; they are whatever text,
+number or blob the application stored, and are dumped as such.

package/docs/supported-objects.md

@@ -1,85 +1,85 @@
-# Supported objects
-
-"Round-trip tested" means the object survives dump → restore and the restored database's
-schema and rows deep-compare equal to the source, across all four paths of the
-interoperability matrix (this package and the native `sqlite3` shell, each dumping and each
-restoring).
-
-## Object matrix
-
-| Object                                 | Dumped | Restored | Round-trip tested | Notes                                                                  |
-| -------------------------------------- | :----: | :------: | :---------------: | ---------------------------------------------------------------------- |
-| Tables                                 |   ✅   |    ✅    |        ✅         | Verbatim stored DDL, so every clause survives.                         |
-| Columns, defaults, collations, `CHECK` |   ✅   |    ✅    |        ✅         | Inline in the table DDL.                                               |
-| Primary keys, `UNIQUE` constraints     |   ✅   |    ✅    |        ✅         | Their automatic indexes are recreated by the table DDL.                |
-| Foreign keys                           |   ✅   |    ✅    |        ✅         | Circular and self-referencing both covered.                            |
-| `INTEGER PRIMARY KEY` (rowid alias)    |   ✅   |    ✅    |        ✅         | The rowid _is_ the column, so it is always kept.                       |
-| Hidden rowids                          |   ✅   |    ⚠️    |        ✅         | Renumbered unless `preserveRowids`; see below.                         |
-| `AUTOINCREMENT` counters               |   ✅   |    ✅    |        ✅         | `sqlite_sequence`, set after the rows.                                 |
-| `WITHOUT ROWID` tables                 |   ✅   |    ✅    |        ✅         |                                                                        |
-| `STRICT` tables                        |   ✅   |    ✅    |        ✅         | SQLite 3.37+ on the restoring side.                                    |
-| Generated columns (`VIRTUAL`/`STORED`) |   ✅   |    ✅    |        ✅         | Not inserted; SQLite recomputes them.                                  |
-| Quoted and keyword names               |   ✅   |    ✅    |        ✅         | `"…"`, `'…'`, `[…]`, keywords, non-ASCII.                              |
-| Indexes                                |   ✅   |    ✅    |        ✅         | Partial, expression, `DESC`, `COLLATE`.                                |
-| Views                                  |   ✅   |    ✅    |        ✅         | Including one created before the table it reads.                       |
-| Triggers                               |   ✅   |    ✅    |        ✅         | Multi-statement bodies; `INSTEAD OF` on views; created after the data. |
-| Virtual tables (FTS5, R-tree, …)       |   ✅   |    ✅    |        ✅         | Shadow tables copied exactly; queryable after restore.                 |
-| Statistics (`sqlite_stat1`/`stat4`)    |   ✅   |    ✅    |        ✅         | `ANALYZE sqlite_schema;` then the rows.                                |
-| `user_version`, `application_id`       |   ⚙️   |    ✅    |        ✅         | With `render.includeDatabaseSettings`; otherwise reported.             |
-| Attached databases                     |   ⚙️   |    ✅    |         —         | One schema per dump: pass `schemaName`.                                |
-| File settings (page size, WAL, …)      |   ❌   |    —     |         —         | See [known-limitations.md](known-limitations.md).                      |
-| Application functions and collations   |   ❌   |    —     |         —         | Registered by the application, not stored in the database.             |
-
-⚙️ = opt-in.
-
-## Model coverage
-
-`introspectSqlite` returns a normalized `SqliteDatabase`:
-
-```ts
-{
-  schemaName, encoding, userVersion, applicationId, pageSize,
-  tables:      SqliteTable[],       // kind (table | virtual | shadow | system), sql, withoutRowid, strict,
-                                    // hasAutoincrement, virtualModule, ownerVirtualTable, rowidAliasColumn, columns
-  indexes:     SqliteIndex[],       // tableName, sql (null for automatic), isUnique, origin, isPartial, columns
-  views:       SqliteView[],
-  triggers:    SqliteTrigger[],     // tableName
-  foreignKeys: SqliteForeignKey[],  // referencedTableName, column pairs, onUpdate, onDelete, match
-  sequences:   SqliteSequence[],    // AUTOINCREMENT counters, as exact text
-}
-```
-
-Per column: `declaredType` as written, `notNull`, `defaultValue` as written,
-`primaryKeyPosition`, and `hidden`/`generated` from `PRAGMA table_xinfo`.
-
-Every object also carries its `sqlite_schema` rowid (`schemaRowid`), which is the order the
-dump uses.
-
-## Notable behaviours
-
-### Hidden rowids
-
-A table without an `INTEGER PRIMARY KEY` still has a rowid, just not a declared column. The
-native `.dump` does not write it, so a restore numbers the rows 1, 2, 3… in dump order —
-closing any gaps deletions left. With `dataExport.preserveRowids` (the native
-`--preserve-rowids`), the rowid is named in each `INSERT` and kept, under the first of
-`rowid`, `_rowid_`, `oid` that is not a real column.
-
-### Triggers
-
-Created after all table data. A trigger created before the load would fire once per
-restored row — an `AFTER INSERT` trigger writing an audit table would fabricate rows the
-source never had. The archive records that as a _hard_ dependency. A trigger whose table is
-not selected is dropped and reported.
-
-### Virtual tables
-
-Recreated the way the native `.dump` does it — by inserting the table's `sqlite_schema` row
-directly, under `PRAGMA writable_schema=ON` — then filling the shadow tables with the
-source's exact rows. The module's constructor never runs, so an FTS5 index or an R-tree
-comes back byte-identical rather than rebuilt. This needs defensive mode off on the
-restoring handle, which the restore arranges and undoes (see
-[restore-api.md](restore-api.md#schemawrites)).
-
-A schema-only dump instead creates each virtual table with its own `CREATE VIRTUAL TABLE`,
-since no shadow rows follow and the module must set up its storage itself.
+# Supported objects
+
+"Round-trip tested" means the object survives dump → restore and the restored database's
+schema and rows deep-compare equal to the source, across all four paths of the
+interoperability matrix (this package and the native `sqlite3` shell, each dumping and each
+restoring).
+
+## Object matrix
+
+| Object                                 | Dumped | Restored | Round-trip tested | Notes                                                                  |
+| -------------------------------------- | :----: | :------: | :---------------: | ---------------------------------------------------------------------- |
+| Tables                                 |   ✅   |    ✅    |        ✅         | Verbatim stored DDL, so every clause survives.                         |
+| Columns, defaults, collations, `CHECK` |   ✅   |    ✅    |        ✅         | Inline in the table DDL.                                               |
+| Primary keys, `UNIQUE` constraints     |   ✅   |    ✅    |        ✅         | Their automatic indexes are recreated by the table DDL.                |
+| Foreign keys                           |   ✅   |    ✅    |        ✅         | Circular and self-referencing both covered.                            |
+| `INTEGER PRIMARY KEY` (rowid alias)    |   ✅   |    ✅    |        ✅         | The rowid _is_ the column, so it is always kept.                       |
+| Hidden rowids                          |   ✅   |    ⚠️    |        ✅         | Renumbered unless `preserveRowids`; see below.                         |
+| `AUTOINCREMENT` counters               |   ✅   |    ✅    |        ✅         | `sqlite_sequence`, set after the rows.                                 |
+| `WITHOUT ROWID` tables                 |   ✅   |    ✅    |        ✅         |                                                                        |
+| `STRICT` tables                        |   ✅   |    ✅    |        ✅         | SQLite 3.37+ on the restoring side.                                    |
+| Generated columns (`VIRTUAL`/`STORED`) |   ✅   |    ✅    |        ✅         | Not inserted; SQLite recomputes them.                                  |
+| Quoted and keyword names               |   ✅   |    ✅    |        ✅         | `"…"`, `'…'`, `[…]`, keywords, non-ASCII.                              |
+| Indexes                                |   ✅   |    ✅    |        ✅         | Partial, expression, `DESC`, `COLLATE`.                                |
+| Views                                  |   ✅   |    ✅    |        ✅         | Including one created before the table it reads.                       |
+| Triggers                               |   ✅   |    ✅    |        ✅         | Multi-statement bodies; `INSTEAD OF` on views; created after the data. |
+| Virtual tables (FTS5, R-tree, …)       |   ✅   |    ✅    |        ✅         | Shadow tables copied exactly; queryable after restore.                 |
+| Statistics (`sqlite_stat1`/`stat4`)    |   ✅   |    ✅    |        ✅         | `ANALYZE sqlite_schema;` then the rows.                                |
+| `user_version`, `application_id`       |   ⚙️   |    ✅    |        ✅         | With `render.includeDatabaseSettings`; otherwise reported.             |
+| Attached databases                     |   ⚙️   |    ✅    |         —         | One schema per dump: pass `schemaName`.                                |
+| File settings (page size, WAL, …)      |   ❌   |    —     |         —         | See [known-limitations.md](known-limitations.md).                      |
+| Application functions and collations   |   ❌   |    —     |         —         | Registered by the application, not stored in the database.             |
+
+⚙️ = opt-in.
+
+## Model coverage
+
+`introspectSqlite` returns a normalized `SqliteDatabase`:
+
+```ts
+{
+  schemaName, encoding, userVersion, applicationId, pageSize,
+  tables:      SqliteTable[],       // kind (table | virtual | shadow | system), sql, withoutRowid, strict,
+                                    // hasAutoincrement, virtualModule, ownerVirtualTable, rowidAliasColumn, columns
+  indexes:     SqliteIndex[],       // tableName, sql (null for automatic), isUnique, origin, isPartial, columns
+  views:       SqliteView[],
+  triggers:    SqliteTrigger[],     // tableName
+  foreignKeys: SqliteForeignKey[],  // referencedTableName, column pairs, onUpdate, onDelete, match
+  sequences:   SqliteSequence[],    // AUTOINCREMENT counters, as exact text
+}
+```
+
+Per column: `declaredType` as written, `notNull`, `defaultValue` as written,
+`primaryKeyPosition`, and `hidden`/`generated` from `PRAGMA table_xinfo`.
+
+Every object also carries its `sqlite_schema` rowid (`schemaRowid`), which is the order the
+dump uses.
+
+## Notable behaviours
+
+### Hidden rowids
+
+A table without an `INTEGER PRIMARY KEY` still has a rowid, just not a declared column. The
+native `.dump` does not write it, so a restore numbers the rows 1, 2, 3… in dump order —
+closing any gaps deletions left. With `dataExport.preserveRowids` (the native
+`--preserve-rowids`), the rowid is named in each `INSERT` and kept, under the first of
+`rowid`, `_rowid_`, `oid` that is not a real column.
+
+### Triggers
+
+Created after all table data. A trigger created before the load would fire once per
+restored row — an `AFTER INSERT` trigger writing an audit table would fabricate rows the
+source never had. The archive records that as a _hard_ dependency. A trigger whose table is
+not selected is dropped and reported.
+
+### Virtual tables
+
+Recreated the way the native `.dump` does it — by inserting the table's `sqlite_schema` row
+directly, under `PRAGMA writable_schema=ON` — then filling the shadow tables with the
+source's exact rows. The module's constructor never runs, so an FTS5 index or an R-tree
+comes back byte-identical rather than rebuilt. This needs defensive mode off on the
+restoring handle, which the restore arranges and undoes (see
+[restore-api.md](restore-api.md#schemawrites)).
+
+A schema-only dump instead creates each virtual table with its own `CREATE VIRTUAL TABLE`,
+since no shadow rows follow and the module must set up its storage itself.

package/package.json

@@ -1,89 +1,96 @@
-{
-  "name": "dbgate-sqlite-dumper",
-  "version": "0.1.0",
-  "description": "Standalone, client-agnostic SQLite SQL dump and restore library for Node.js, compatible with the native sqlite3 .dump command",
-  "type": "module",
-  "license": "GPL-3.0-only",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/dbgate/dbgate-sqlite-dumper.git"
-  },
-  "bugs": {
-    "url": "https://github.com/dbgate/dbgate-sqlite-dumper/issues"
-  },
-  "homepage": "https://github.com/dbgate/dbgate-sqlite-dumper#readme",
-  "engines": {
-    "node": ">=20"
-  },
-  "files": [
-    "LICENSE",
-    "README.md",
-    "dist",
-    "docs"
-  ],
-  "main": "./dist/index.cjs",
-  "module": "./dist/index.js",
-  "types": "./dist/index.d.ts",
-  "exports": {
-    ".": {
-      "types": "./dist/index.d.ts",
-      "import": "./dist/index.js",
-      "require": "./dist/index.cjs"
-    },
-    "./better-sqlite3": {
-      "types": "./dist/better-sqlite3.d.ts",
-      "import": "./dist/better-sqlite3.js",
-      "require": "./dist/better-sqlite3.cjs"
-    }
-  },
-  "scripts": {
-    "build": "tsup",
-    "clean": "tsup --clean",
-    "format": "prettier --write .",
-    "format:check": "prettier --check .",
-    "lint": "eslint . --max-warnings 0",
-    "prepublishOnly": "npm run lint && npm run typecheck && npm test && npm run build && node scripts/smoke.mjs",
-    "test": "vitest run",
-    "test:all": "npm run test && npm run test:integration",
-    "test:integration": "vitest run --config vitest.integration.config.ts",
-    "test:package": "npm run build && node scripts/smoke.mjs",
-    "test:watch": "vitest",
-    "typecheck": "tsc --noEmit"
-  },
-  "keywords": [
-    "sqlite",
-    "sqlite3",
-    "dump",
-    ".dump",
-    "sql",
-    "backup",
-    "restore",
-    "database",
-    "better-sqlite3"
-  ],
-  "sideEffects": false,
-  "publishConfig": {
-    "access": "public",
-    "provenance": true
-  },
-  "peerDependencies": {
-    "better-sqlite3": ">=9.0.0"
-  },
-  "peerDependenciesMeta": {
-    "better-sqlite3": {
-      "optional": true
-    }
-  },
-  "devDependencies": {
-    "@eslint/js": "^9.25.1",
-    "@types/better-sqlite3": "^7.6.13",
-    "@types/node": "^22.15.3",
-    "better-sqlite3": "^12.2.0",
-    "eslint": "^9.25.1",
-    "prettier": "^3.5.3",
-    "tsup": "^8.4.0",
-    "typescript": "^5.8.3",
-    "typescript-eslint": "^8.31.0",
-    "vitest": "^3.1.2"
-  }
-}
+{
+  "name": "dbgate-sqlite-dumper",
+  "version": "0.1.1",
+  "description": "Standalone, client-agnostic SQLite SQL dump and restore library for Node.js, compatible with the native sqlite3 .dump command, with adapters for better-sqlite3 and Cloudflare D1",
+  "type": "module",
+  "license": "GPL-3.0-only",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/dbgate/dbgate-sqlite-dumper.git"
+  },
+  "bugs": {
+    "url": "https://github.com/dbgate/dbgate-sqlite-dumper/issues"
+  },
+  "homepage": "https://github.com/dbgate/dbgate-sqlite-dumper#readme",
+  "engines": {
+    "node": ">=20"
+  },
+  "files": [
+    "LICENSE",
+    "README.md",
+    "dist",
+    "docs"
+  ],
+  "main": "./dist/index.cjs",
+  "module": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js",
+      "require": "./dist/index.cjs"
+    },
+    "./better-sqlite3": {
+      "types": "./dist/better-sqlite3.d.ts",
+      "import": "./dist/better-sqlite3.js",
+      "require": "./dist/better-sqlite3.cjs"
+    },
+    "./d1": {
+      "types": "./dist/d1.d.ts",
+      "import": "./dist/d1.js",
+      "require": "./dist/d1.cjs"
+    }
+  },
+  "scripts": {
+    "build": "tsup",
+    "clean": "tsup --clean",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "lint": "eslint . --max-warnings 0",
+    "prepublishOnly": "npm run lint && npm run typecheck && npm test && npm run build && node scripts/smoke.mjs",
+    "test": "vitest run",
+    "test:all": "npm run test && npm run test:integration",
+    "test:integration": "vitest run --config vitest.integration.config.ts",
+    "test:package": "npm run build && node scripts/smoke.mjs",
+    "test:watch": "vitest",
+    "typecheck": "tsc --noEmit"
+  },
+  "keywords": [
+    "sqlite",
+    "sqlite3",
+    "dump",
+    ".dump",
+    "sql",
+    "backup",
+    "restore",
+    "database",
+    "better-sqlite3",
+    "cloudflare",
+    "d1"
+  ],
+  "sideEffects": false,
+  "publishConfig": {
+    "access": "public",
+    "provenance": true
+  },
+  "peerDependencies": {
+    "better-sqlite3": ">=9.0.0"
+  },
+  "peerDependenciesMeta": {
+    "better-sqlite3": {
+      "optional": true
+    }
+  },
+  "devDependencies": {
+    "@eslint/js": "^9.25.1",
+    "@types/better-sqlite3": "^7.6.13",
+    "@types/node": "^22.15.3",
+    "better-sqlite3": "^12.2.0",
+    "eslint": "^9.25.1",
+    "prettier": "^3.5.3",
+    "tsup": "^8.4.0",
+    "typescript": "^5.8.3",
+    "typescript-eslint": "^8.31.0",
+    "vitest": "^3.1.2"
+  }
+}