Gap (d): Turso / libsql driver in Prisma Next
Parent epic: #313 — Migrate NetScript DB layer to Prisma Next (Postgres-first pilot).
Upstream status (verified 2026-07-03, prisma/prisma-next @ v0.14.0)
ABSENT. No libsql/Turso driver. Prisma Next's SQLite target is Node node:sqlite (path/memory
bindings only). SQLite itself was downgraded to "proof of concept" earlier in the roadmap.
Why NetScript needs it (low priority)
The original epic premise that NetScript wires Turso via @tursodatabase/database + --allow-ffi was
false — Turso is not actually wired today (SQLite is scaffold-only, adapter-less). So there is
nothing to preserve or port. This gap is only relevant if NetScript later decides to add a
first-class Turso/libsql engine.
When this lands → we can do
If/when both (1) a Prisma Next libsql/Turso driver ships AND (2) NetScript decides to add Turso to its
supported matrix → scope a Turso pilot axis. Otherwise this stays a no-op watch item.
Re-check mechanism
Low-cadence (quarterly, or when a Turso requirement surfaces): check releases for a libsql/Turso
driver. No action unless NetScript adds Turso to scope.
Labels: area:database, area:deps, wave:defer, status:triage.
Part of #313
Gap (d): Turso / libsql driver in Prisma Next
Parent epic: #313 — Migrate NetScript DB layer to Prisma Next (Postgres-first pilot).
Upstream status (verified 2026-07-03, prisma/prisma-next @ v0.14.0)
ABSENT. No libsql/Turso driver. Prisma Next's SQLite target is Node
node:sqlite(path/memorybindings only). SQLite itself was downgraded to "proof of concept" earlier in the roadmap.
Why NetScript needs it (low priority)
The original epic premise that NetScript wires Turso via
@tursodatabase/database+--allow-ffiwasfalse — Turso is not actually wired today (SQLite is scaffold-only, adapter-less). So there is
nothing to preserve or port. This gap is only relevant if NetScript later decides to add a
first-class Turso/libsql engine.
When this lands → we can do
If/when both (1) a Prisma Next libsql/Turso driver ships AND (2) NetScript decides to add Turso to its
supported matrix → scope a Turso pilot axis. Otherwise this stays a no-op watch item.
Re-check mechanism
Low-cadence (quarterly, or when a Turso requirement surfaces): check releases for a libsql/Turso
driver. No action unless NetScript adds Turso to scope.
Labels:
area:database,area:deps,wave:defer,status:triage.Part of #313