| 维度 |
| | Prisma | Prisma |
| Query EngineRust 查询引擎
删除
改为 TypeScript Query CompilerGenerator
|
| prisma-client-js
prisma-client
| |
|
|
| CJS/ESM 可选
|
|
|
This means that troublesome Rust query‑engine binaries disappeared entirely. However cost was a complete rewrite of database integration layer.
The boundary to clarify:
Prima removes its own Rust query‑engine binaries . That does not mean “no native dependency” – because Prisma now forces you to use a Driver Adapter. The recommended SQLite adapter is `@prisma/adapter-娱乐ter-sqlite3` which depends on native C++ module `娱乐er‑sqlite3` and will still bundle a platform‑specific `.node` file.
再看逆流而动，当整个前端都在“锈化”，Prisma 却在“去锈”中去掉 Rust 引擎二进制。
A quick industry backdrop:
-
Bundlers: esbuild,SWC。Turbopack/Rspack/Rolldown
-
Linter/Formatter: Biome/Oxc
-
CSS tools: Lightning CSS
The trend is clear – “use Rust for performance”. JavaScript tools are slow;switching to native binaries can boost build speed tenfold. Our project benefits from esbuild and Vite's Rust‑based core.
A seemingly opposite move by Prisma – removing its long‑standing Rust query engine – looks like going against that trend. But both moves share same goal:
-
The front end keeps Rust in build phase so that end users receive pure JS/CSS bundles without native baggage.
-
Prisma takes Rust out of runtime distribution so that no platform‑specific binaries have to ship with your app.
-
This aligns in direction even though y happen on opposite sides of stack.
关键决策的观点是，用什么 Driver Adapter？
The official recommendation was `@prisma/adapter-娱乐ter-sqlite3` but we found issues:
-
`娱乐ter-sqlite3` is a native C++ addon requiring `electron-rebuild` for each Electron ABI.
-
You must set `asarUnpack` for `.node` files – anor path nightmare.
-
A new Electron or CI architecture triggers anor rebuild cycle.
The turning point came when Node.js introduced an internal module `node:sqlite`. As long as your bundled Electron provides Node ≥ `,you can use it without any native compilation—no rebuilds needed!其实，
If you’re ready for this small shift in dependency responsibility,we built our own driver adapter around `node:sqlite` and replaced `@prisma/adapter-娱乐ter-sqlite3`. This unlocked a cleaner build process and eliminated all platform binaries from your installer payload.
说到实现。基于 node:sqlite 的 Driver Adapter
自定义 Adapter 主要代码
// packages/common/src/utils/prisma/nodeSqliteAdapter.js
const { DatabaseSync } = require
const {
ColumnTypeEnum,DriverAdapterError,} = require
// SQLite error codes used by node:sqlite
const SQLITE_CONSTRAINT_UNIQUE = /*…*/
const SQLITE_CONSTRAINT_PRIMARYKEY= /*…*/
const SQLITE_CONSTRAINT_NOTNULL = /*…
*/
const SQLITE_CONSTRAINT_FOREIGNKEY= /*…*/
const SQLITE_BUSY = /*…*/
class NodeSqliteQueryable {
constructor {
this.db = db
this.adapterOptions= adapterOptions
}
async queryRaw {
const { columnNames,declaredTypes,values } =
this.performIO
const columnTypes =
getColumnTypes
return {
columnNames,columnTypes,rows : values.map)
}
}
performIO {
const args =
query.args.map=> mapArg(arg,query.argTypes,this.adapterOptions))
const stmt=this.db.prepare
stmt.setReadBigInts
let columns=
try{ columns=stmt.columns }catch{ /* non‑SELECT returns */ }
if{
stmt.run
return{columnNames :。declaredTypes :,values :}
}
stmt.setReturnArrays
return{
declaredTypes :columns.map,columnNames :columns.map,values :stmt.all
}
}
onError{ throw new DriverAdapterError) }
}
// Error mapping 娱乐ween node:sqlite & 娱乐ter-sqlite3
function convertDriverError{
// node::sqlite error.code === 'ERR_SQLITE_ERROR'
// real code in error.errcode
const extended =
typeof error.errcode==='number'?话说回来，error.errcode:void
if{
return{ kind:'SocketTimeout' }
}
if(extended===SQLITE_CONSTRAINT_UNIQUE ||
extended===SQLITE_CONSTRAINT_PRIMARYKEY){
return{
kind的观点是。'UniqueConstraintViolation',constraint:{ fields :parseConstraintFields }
}
}
//…map or codes here
throw error
}
// Factory adhering to SqlMigrationAwareDriverAdapterFactory interface
class PrismaNodeSqlite {
constructor{
this.config=config
this.options=options
}
connect{
const dbPath=this.config.url.replace
const db=new DatabaseSync
// WAL mode for concurrent reads/writes when not memory DB
if{
db.exec
}
db.exec
db.exec
return Promise.resolve(
new PrismaNodeSqliteAdapter)
}
}
module.exports={ PrismaNodeSqlite }
运行时连接方式
// packages/common/src/utils/prisma/index.js
const { PrismaClient } = require
const { PrismaNodeSqlite } = require
function getPrisma{
if return global.prisma
const { dbUrl }=getD娱乐onstants
// No query engine binary required
const adapter=new PrismaNodeSqlite
const prisma=new PrismaClient({
adapter,log:
})
global.prisma=prisma
return prisma
}
Schema 与配置的分离
// packages/common/src/prisma/schema.prisma
generator client{
provider ="prisma-client"
output ="../generated/db_client"
runtime ="nodejs"
importFileExtension =""
}
datasource db{
provider ="sqlite"
// URL removed – runtime uses adapter;CLI uses prisma.config.ts
}
// packages/common/prisma.config.ts
import { defineConfig } from 'prisma/config'
export default defineConfig({
再看schema。'./src/prima/schema.prima',migrations:{path:'./src/prima/migrations'},datasource:{
url:
}
})
迁移从 fork CLI 到直接执行 SQL
No more ``schema-engine-windows.exe`;we read migration files directly via `node:sqlite`:
javascript
// packages/common/src/utils/prisma/runPrismaCommand.js
const { DatabaseSync}=require
async function runPrismaCommand{
/* ... fetch migrations dir ... */
}
**The big picture:** By shifting migration logic into plain SQL files executed at runtime we eliminate any need for binary engines altoger.
