Property '$on' is missing in type about nestjs-prisma

[marcjulian]

Hi @JoshuaM1995 have a look at the extensions example which uses $on with an extended PrismaClient

Extended Prisma Client

nestjs-prisma/examples/extensions/src/prisma.extension.ts

Lines 3 to 13 in 2b93c9e

	export const extendedPrismaClient = new PrismaClient<
	Prisma.PrismaClientOptions,
	'query' | 'info' | 'warn' | 'error'
	>({
	log: [
	{ level: 'query', emit: 'event' },
	{ level: 'info', emit: 'event' },
	{ level: 'warn', emit: 'event' },
	{ level: 'error', emit: 'event' },
	],
	}).$extends({

Use $on

nestjs-prisma/examples/extensions/src/main.ts

Line 13 in 2b93c9e

customPrismaService.client.$on('error', (e) => {});

[marcjulian]

I tested the extensions example with the latest prisma version 4.16.1 and I am seeing the same error as you:

src/prisma.extension.ts:25:22 - error TS2339: Property '$on' does not exist on type 'DynamicClientExtensionThis<TypeMap<Args & { result: {}; model: { user: { findByEmail: () => (email: string) => Promise<GetResult<{ id: string; email: string; name: string; }, { [x: string]: () => unknown; }> & {}>; }; }; query: {}; client: {}; }>, TypeMapCb, { ...; }>'.

25 extendedPrismaClient.$on('query', (e) => {});

This might be an issue with the latest prisma version. Either $on is missing in the types or it is not available any longer for extended PrismaClients.

[marcjulian]

@JoshuaM1995 I found the following issue about disallowing $on for extended clients: prisma/prisma#19552 (comment)

You can find it also in the release notes from 4.16.0

[JoshuaM1995]

@JoshuaM1995 I found the following issue about disallowing $on for extended clients: prisma/prisma#19552 (comment)

You can find it also in the release notes from 4.16.0

Thanks for looking into this. Are there any plans for supporting Prisma 4.16.0 any time soon? I can help contribute if possible.

If not I can try downgrading. That was the first thing I tried, but even after downgrading @prisma/client and prisma in my package.json files (I'm in a monorepo), I still see it generating the client with 4.16.0. I even tried using npx to generate it with a specific version of the cli, with no luck.

[JoshuaM1995]

Also, maybe it would be safer to lock prisma to a patch version in the package.json? @marcjulian

"@prisma/client": "~4.13.0"

[JoshuaM1995]

Update: I was able to solve this temporarily with PNPM by adding this to my package.json:

"pnpm": {
    "overrides": {
      "@prisma/client": "4.15.0",
      "prisma": "4.15.0"
    }
  }

[marcjulian]

@JoshuaM1995 I have update it to the latest prisma client and added support for extension GA. Please try it out with the latest dev release:

npm i [email protected]

[marcjulian]

This has been released with 0.21.0