@seta-labs/nestjs-prisma

Prisma for NestJS APIs on Postgres (Prisma 7, @prisma/adapter-pg): the app's PrismaService built on its own generated client, a database health indicator for @seta-labs/nestjs-health, and the predicates repositories use to translate P2002/P2025 ([L1]). Optional: BLUEPRINT.md states the contracts, this package is one way to meet them.

Install

pnpm add @seta-labs/nestjs-prisma

Peer dependency: @nestjs/common. The package imports nothing from Prisma: the app passes its generated PrismaClient and PrismaPg.

Wire it

// src/prisma/prisma.service.ts: stays in the app, where the client is generated
import { Injectable } from '@nestjs/common';
import { PrismaClient, PrismaPg } from '@acme/db';
import { prismaService } from '@seta-labs/nestjs-prisma';

@Injectable()
export class PrismaService extends prismaService(PrismaClient, { adapter: PrismaPg }) {}

// app.module.ts
import { HealthModule } from '@seta-labs/nestjs-health';
import { DatabaseHealthIndicator, PrismaModule } from '@seta-labs/nestjs-prisma';

@Module({
    imports: [
        PrismaModule.forRoot({ service: PrismaService }), // global: inject PrismaService anywhere
        HealthModule.forRoot({ service: 'my-api', indicators: [DatabaseHealthIndicator] }),
    ],
})
export class AppModule {}

What the service does on top of the generated client:

• DATABASE_URL is required at construction (a clear boot error, not a failed first query); its ?schema= becomes the adapter schema.
• Pool: max from PG_POOL_MAX (default 10), idleTimeoutMillis 30_000, connectionTimeoutMillis 5_000 so an exhausted pool fails fast instead of queueing forever. Override with pool: { … }, or the URL with connectionString.
• Interactive transactions run their queries one after the other (serializeTransactionQueries): Prisma 7 may otherwise overlap them on the transaction's single connection and leave it stuck. serializeTransactions: false turns it off.
• $connect on module init and $disconnect on shutdown, logged through the Nest Logger.

Translate errors in repositories

import { ConflictException, NotFoundException } from '@nestjs/common';
import { isRecordNotFound, isUniqueViolation } from '@seta-labs/nestjs-prisma';

try {
    return await this.prisma.order.create({ data });
} catch (err: unknown) {
    if (isUniqueViolation(err, 'uq_orders_code')) throw new ConflictException('Order code taken');
    throw err;
}

isUniqueViolation(err, constraint?) finds the constraint in meta.target, or, when Prisma 7 with the pg adapter leaves it empty, in the driver message and the constraint columns. isRecordNotFound(err) matches P2025.