Prisma 7 Setup

Five nestarc packages now have first-class Prisma 7 support: tenancy 0.14, soft-delete 0.6, audit-log 0.3, feature-flag 0.5, and pagination 0.3.

Compatibility Matrix

Package	Release	Supported Prisma majors	Prisma 7 status
@nestarc/tenancy	0.14.0	6, 7	Primary development and E2E target
@nestarc/soft-delete	0.6.0	5, 6, 7	Primary development and PostgreSQL E2E target
@nestarc/audit-log	0.3.0	5, 6, 7	Primary development and CI target
@nestarc/feature-flag	0.5.0	7	Required Prisma major
@nestarc/pagination	0.3.0	5, 6, 7	Primary development and CI target

Prisma 7 requires Node.js 20.19+, 22.12+, or 24+. Individual package engine ranges are listed on each installation page.

Install the PostgreSQL Adapter

Prisma 7 direct PostgreSQL connections use a driver adapter:

npm install @prisma/client @prisma/adapter-pg pg dotenv
npm install --save-dev prisma

Generate the Client

Use the prisma-client generator with an explicit output path. Keep the connection URL out of schema.prisma:

// prisma/schema.prisma
generator client {
  provider = "prisma-client"
  output   = "../src/generated/prisma"
}

datasource db {
  provider = "postgresql"
}

Move the CLI datasource URL into Prisma Config:

// prisma.config.ts
import 'dotenv/config';
import { defineConfig, env } from 'prisma/config';

export default defineConfig({
  schema: 'prisma/schema.prisma',
  migrations: { path: 'prisma/migrations' },
  datasource: { url: env('DATABASE_URL') },
});

Generate the client after changing the schema:

npx prisma generate

Create the Runtime Client

Import PrismaClient from the configured output instead of the @prisma/client root:

import { PrismaPg } from '@prisma/adapter-pg';
import { PrismaClient } from './generated/prisma/client';

const adapter = new PrismaPg({
  connectionString: process.env.DATABASE_URL!,
});

export const prisma = new PrismaClient({ adapter });

Pass this client or one of its model delegates to nestarc exactly as you did with Prisma 6.

Package-Specific Steps

tenancy

Apply createPrismaTenancyExtension() to the generated base client. Prisma 6 applications can keep their current client construction. tenancy 0.14 no longer supports Prisma 5.

soft-delete

Cascade and relation filters require explicit DMMF metadata. Install @prisma/internals at exactly the same version as prisma, load the schema with getDMMF(), and pass the result as dmmf to both the extension and module configuration. Basic soft-delete filtering without cascade or relation filters does not need DMMF.

See soft-delete installation.

audit-log

The Prisma 7 generated client exports its Prisma namespace from the generated output. Pass that namespace to both the extension and module:

import { Prisma, PrismaClient } from './generated/prisma/client';

export const prismaModule = { Prisma };

const client = base.$extends(createAuditExtension({
  trackedModels: ['User'],
  prismaModule,
}));

Also pass prismaModule to AuditLogModule.forRoot() or forRootAsync().

feature-flag

feature-flag 0.5 requires Prisma 7. Create the generated client with a driver adapter, then pass it through the existing prisma module option. No database migration is required when upgrading from 0.4.

pagination

Pagination accepts a normal Prisma model delegate, so the pagination API does not change. Only standalone client construction changes for Prisma 7.

Upgrade Checklist

1. Upgrade to the package releases in the compatibility matrix.
2. Use a Prisma 7-compatible Node.js version.
3. Move the datasource URL into prisma.config.ts.
4. Switch to provider = "prisma-client" and set an explicit output.
5. Install the adapter for your database and pass it to PrismaClient.
6. Update imports to the generated client path.
7. Apply the soft-delete or audit-log package-specific configuration above.
8. Regenerate the client and run type, integration, and migration checks before deployment.

Prisma 6 consumers of tenancy, soft-delete, audit-log, and pagination do not need to adopt the Prisma 7 client layout until they upgrade Prisma itself.