Skip to content

chore(deps): update dependencies, better-sqlite3 to v13 - #96

Merged
mikevalstar merged 1 commit into
mainfrom
chore/dep-updates-2026-08
Aug 16, 2026
Merged

chore(deps): update dependencies, better-sqlite3 to v13#96
mikevalstar merged 1 commit into
mainfrom
chore/dep-updates-2026-08

Conversation

@mikevalstar

Copy link
Copy Markdown
Owner

Tracked in AETH-updmqqig.

Minor / patch

Package From To
@assistant-ui/react-ai-sdk 1.4.4 1.4.5
@biomejs/biome (dev) 2.5.7 2.5.8
@tanstack/react-devtools 0.10.9 0.10.10
globby 16.2.2 16.2.3
mailparser 3.9.14 3.9.15
sonner 2.0.7 2.0.8
zustand 5.0.14 5.0.15

Major

Package From To
better-sqlite3 12.11.1 13.0.3
@types/better-sqlite3 (dev) 7.6.13 9.6.0

better-sqlite3 13.0.0 is an N-API rewrite: prebuilt binaries now ship inside the package, prebuild-install is gone, and Node >=22 is required (we're on 24). The public API is unchanged — only additions (db.explain(), statement.toString()).

The one real risk was sqlite-vec, which loads a native extension into the better-sqlite3 handle in src/lib/embeddings/db.ts. Smoke-tested against the v13 build: extension loads (vec_version()v0.1.9), vec0 virtual table creates, and a KNN MATCH ... AND k = 1 query returns correctly.

Known tradeoff

@prisma/adapter-better-sqlite3@7.9.1 has better-sqlite3: ^12.6.0 as a hard dependency (not a peer), so the tree now carries two native copies — v12 under the adapter for the Prisma-managed main DB, v13 at the root for the embeddings sidecar. Both build and run fine, but install is heavier. This collapses on its own once Prisma widens the range; worth reverting better-sqlite3 to ^12 instead if the duplicate build is unwelcome.

Verification

  • pnpm type-check — clean
  • pnpm test — 59 passed (8 files)
  • pnpm check — exit 0 (2 pre-existing warnings, unchanged)
  • pnpm build — succeeds
  • pnpm debug doctor — DB connects through the Prisma adapter, 2 users read

🤖 Generated with Claude Code

Patch/minor bumps: @assistant-ui/react-ai-sdk 1.4.5, @biomejs/biome 2.5.8,
@tanstack/react-devtools 0.10.10, globby 16.2.3, mailparser 3.9.15,
sonner 2.0.8, zustand 5.0.15.

Major: better-sqlite3 12 -> 13 (N-API rewrite, prebuilt binaries shipped in
package, prebuild-install dropped) plus @types/better-sqlite3 7 -> 9. The
public API is unchanged; verified sqlite-vec 0.1.9 still loads as an
extension and KNN queries work against the v13 build.

Note: @prisma/adapter-better-sqlite3 7.9.1 hard-depends on better-sqlite3
^12.6.0, so the tree now carries two native copies — v12 for Prisma, v13 for
the embeddings sidecar (src/lib/embeddings/db.ts). Collapses once Prisma
widens its range.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mikevalstar
mikevalstar merged commit 8b2f32d into main Aug 16, 2026
2 checks passed
@kilo-code-bot

kilo-code-bot Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)
  • package.json - Dependency version updates
  • pnpm-lock.yaml - Lockfile updates reflecting dependency changes

Review Notes

This PR updates multiple dependencies:

Minor/Patch Updates:

  • @assistant-ui/react-ai-sdk: 1.4.4 → 1.4.5
  • @biomejs/biome: 2.5.7 → 2.5.8 (dev)
  • @tanstack/react-devtools: 0.10.9 → 0.10.10
  • globby: 16.2.2 → 16.2.3
  • mailparser: 3.9.14 → 3.9.15
  • sonner: 2.0.7 → 2.0.8
  • zustand: 5.0.14 → 5.0.15

Major Updates:

  • better-sqlite3: ^12.11.1 → ^13.0.3
  • @types/better-sqlite3: ^7.6.13 → ^9.6.0 (dev)

The major version bump for better-sqlite3 from v12 to v13 is an N-API rewrite with prebuilt binaries shipped in the package. The public API remains unchanged per the PR description, and the author has already smoke-tested the sqlite-vec extension compatibility. The types package major version bump correctly aligns with the underlying library version.

All verification steps (type-check, test, build, doctor) have passed as documented in the PR.


Reviewed by kimi-k2.5 · Input: 163.8K · Output: 2K · Cached: 0

mikevalstar added a commit that referenced this pull request Aug 16, 2026
Resolves the package.json / pnpm-lock.yaml conflicts. This branch was cut
before #94, #91, and #96 landed, so most of its 38 bumps are already in main
and several of its targets are now *older* than main (nanoid 5 vs 6,
typescript 6 vs 7, jsdom 29 vs 30, better-sqlite3 12 vs 13, biome 2.5.7 vs
2.5.8, zustand 5.0.14 vs 5.0.15, @tanstack/react-devtools 0.10.9 vs 0.10.10,
@types/better-sqlite3 7 vs 9).

Resolution takes main's package.json as the base and re-applies only the
bumps where this branch is genuinely ahead:

  @ai-sdk/anthropic         ^4.0.34  -> ^4.0.36
  @ai-sdk/react             ^4.0.59  -> ^4.0.61
  @assistant-ui/react       ^0.15.8  -> ^0.15.12
  @assistant-ui/react-markdown ^0.14.9 -> ^0.14.10
  @tanstack/router-plugin   ^1.168.26 -> ^1.168.28
  ai                        ^7.0.56  -> ^7.0.58
  exa-js                    ^2.16.3  -> ^2.17.0
  imapflow                  ^1.6.5   -> ^1.6.6
  lucide-react              ^1.30.0  -> ^1.31.0
  @types/node               ^26.1.2  -> ^26.2.0
  tsx                       ^4.23.10 -> ^4.23.11

Lockfile regenerated from main's rather than hand-merged.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mikevalstar
mikevalstar deleted the chore/dep-updates-2026-08 branch August 16, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant