4 mismatches found
01Undocumented adapter factory exports
packages/adapter-better-sqlite3/src/index.ts, packages/adapter-mariadb/src/index.ts, packages/adapter-mssql/src/index.ts, packages/adapter-neon/src/index.ts, packages/adapter-pg/src/index.ts, packages/adapter-planetscale/src/index.ts, packages/adapter-ppg/src/index.ts
mediumIn the code
export { PrismaBetterSqlite3AdapterFactory as PrismaBetterSqlite3 } from './better-sqlite3' // L1
export { PrismaMariaDbAdapterFactory as PrismaMariaDb } from './mariadb' // L1
export { PrismaMssqlAdapterFactory as PrismaMssql } from './mssql' // L1
export { PrismaNeonAdapterFactory as PrismaNeon } from './neon' // L1
export { PrismaNeonHttpAdapterFactory as PrismaNeonHttp } from './neon' // L1
export { PrismaPgAdapterFactory as PrismaPg } from './pg' // L1
export { PrismaPlanetScaleAdapterFactory as PrismaPlanetScale } from './planetscale' // L1
export { PrismaPostgresAdapter } from './ppg' // L1
In the docs
(not documented)
The code exports multiple adapter factory classes (PrismaBetterSqlite3, PrismaMariaDb, PrismaMssql, PrismaNeon, PrismaNeonHttp, PrismaPg, PrismaPlanetScale, PrismaPostgresAdapter) from dedicated adapter packages, but the provided documentation does not mention these exports or how to use them. Developers looking to use custom database adapters would not know these APIs exist.
Suggested fix
Add documentation for each adapter factory export, including: (1) what each adapter is for, (2) how to import it, (3) example usage with PrismaClient configuration, and (4) links to the respective adapter package documentation (e.g., @prisma/adapter-better-sqlite3, @prisma/adapter-pg, etc.).
02Undocumented bundled JavaScript driver exports
packages/bundled-js-drivers/src/index.ts
mediumIn the code
export { libSql } // L6
export { neon } // L6
export { pg } // L6
export { planetScale } // L6
In the docs
(not documented)
The @prisma/bundled-js-drivers package exports libSql, neon, pg, and planetScale driver instances, but the provided documentation contains no mention of these exports or how developers should use them in conjunction with the adapter factories.
Suggested fix
Add documentation explaining: (1) what bundled JavaScript drivers are, (2) when to use them vs. native drivers, (3) how to import and pass them to adapter factories, and (4) examples for each driver (libSql, neon, pg, planetScale).
03Undocumented client-common and client-engine-runtime exports
packages/client-common/src/index.ts, packages/client-engine-runtime/src/index.ts
lowIn the code
export * from './Cache' // L1
export * from './casing' // L2
export * from './client-config' // L3
export * from './Dictionary' // L4
export * from './dmmf' // L5
export * from './enums' // L6
export * from './lazyProperty' // L7
export * from './omit' // L8
export * from './operations' // L9
export * from './QueryCompiler' // L10
export * from './QueryEngine' // L11
export * from './runtimeDataModel' // L12
export * from './uniqueBy' // L13
export * from './batch' // L1
export { QueryEvent } from './events' // L2
export { DataMapperError } from './interpreter/data-mapper' // L3
export { QueryInterpreter } from './interpreter/query-interpreter' // L4
export { type QueryInterpreterOptions } from './interpreter/query-interpreter' // L4
export { TransactionInfo } from './transaction-manager/transaction' // L17
export { Options as TransactionOptions } from './transaction-manager/transaction' // L17
export { TransactionManager } from './transaction-manager/transaction-manager' // L18
In the docs
(not documented)
The @prisma/client-common and @prisma/client-engine-runtime packages export numerous types and classes (QueryInterpreter, TransactionManager, QueryEvent, DataMapperError, DMMF, etc.) that appear to be part of the public API for advanced use cases and extensions. None of these are mentioned in the provided documentation.
Suggested fix
Create or update documentation for these advanced/internal packages explaining: (1) the purpose of each package, (2) intended use cases (e.g., building extensions, custom query tools), (3) which exports are stable vs. internal, and (4) example usage patterns. Consider adding a "Advanced / Internal APIs" section if these are not meant for general use.
04Undocumented client generator exports
packages/client-generator-js/src/index.ts
lowIn the code
export { generateClient } from './generateClient' // L1
export { type GenerateClientOptions } from './generateClient' // L1
export { PrismaClientJsGenerator } from './generator' // L2
export { getDMMF } from './getDMMF' // L3
export { dmmfToTypes } from './utils/types/dmmfToTypes' // L4
In the docs
(not documented)
The @prisma/client-generator-js package exports generateClient, PrismaClientJsGenerator, getDMMF, and dmmfToTypes. These appear to be APIs for programmatically generating or introspecting Prisma Client, but are not documented in the provided documentation.
Suggested fix
Add documentation explaining: (1) what these utilities are for (e.g., custom code generation, DMMF introspection), (2) when and how to use them, (3) API signatures and examples, and (4) whether they are stable or internal APIs.