Should we consider prisma 7.x not usable with NestJS?

[cantoute]

Question

I've seemed to try all possible ways (myself / codex 5.2 / claude 4.5) to use Prisma 7.3 with NestJS (v11)

Is it possible without making a big mess ?
Should I wait and continu using Prisma 6?

How to reproduce (optional)

No response

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

No response

[Irupt]

It works perfectly for me with NestJS 11. What's wrong with it? Please provide more information.

[nurul3101]

This repository had NestJS examples with Prisma 7 which you can use as a reference:

https://github.com/prisma/prisma-examples

[cantoute]

Thanks

So I don't understand why I failed previous times... But example helped.

Perhaps I got trapped as I had prisma 6.x as global client that was confusing file linting

[nferdica]

Prisma 7 works perfectly fine with NestJS 11. The key difference from v6 is that the new prisma-client generator emits TypeScript files, so the integration pattern changes slightly.

Here's a clean setup:

1. Schema (prisma/schema.prisma):

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

2. PrismaService:

// src/prisma/prisma.service.ts
import { Injectable, OnModuleInit, OnModuleDestroy } from '@nestjs/common'
import { PrismaClient } from '../generated/prisma/client'

@Injectable()
export class PrismaService extends PrismaClient implements OnModuleInit, OnModuleDestroy {
  async onModuleInit() {
    await this.$connect()
  }

  async onModuleDestroy() {
    await this.$disconnect()
  }
}

3. PrismaModule:

// src/prisma/prisma.module.ts
import { Global, Module } from '@nestjs/common'
import { PrismaService } from './prisma.service'

@Global()
@Module({
  providers: [PrismaService],
  exports: [PrismaService],
})
export class PrismaModule {}

4. Use it anywhere:

@Injectable()
export class UsersService {
  constructor(private prisma: PrismaService) {}

  findAll() {
    return this.prisma.user.findMany()
  }
}

The only thing that might trip you up: if you use $extends(), it returns a new instance rather than mutating the original. The cleanest pattern for that in NestJS is:

function extendedPrismaClient() {
  const client = new PrismaClient().$extends(/* your extensions */)
  return class {
    constructor() { return client }
  } as new () => typeof client
}

@Injectable()
export class PrismaService extends extendedPrismaClient() implements OnModuleInit {
  async onModuleInit() { await this.$connect() }
}

This approach is well-tested and used in production. No "big mess" required.

[BghAek]

does this work for you without changing module and moduleResolution from nodenest to commonjs ?