NotFoundError not exported

[PatrikValkovic]

Bug description

When user uses rejectOnNotFound or findFirstOrThrow/findUniqueOrThrow, there is no way how to catch this exception specifically. Because Prisma doesn't export NotFoundError, user can't use instance operator and therefore can decide only based on the error message.

I believe the NotFoundError should be exported and therefore I set this up as a bug.

How to reproduce

Run prisma generate and inspect the generated file.

Expected behavior

There is NotFoundError exported, so the user can decide using check error instanceof Prisma.NotFoundError.

Prisma information

No schema or queries are neccessary.

Environment & setup

Is environment agnostic.

Prisma Version

I tried prisma clients in versions 3.13.0, 3.15.2 and 4.0.0.

[janpio]

I think this was already fixed via #14076 Agree?
It should be available in the current dev version for testing, and later this month in Prisma 4.1.0.

[janpio]

@PatrikValkovic Can you confirm that the PR above solved your problem?

[miguelff]

@PatrikValkovic NotFoundError was an implementation detail when findFirstOrThrow and findUniqueOrThrow where emulated on the client rather than implemented on the engine. Since 4.6.0, the error became deprecated and converted to a PrismaClientKnownRequestError. If you needed to perform conditional checks on this type of error, you could rely on its error code. The one for this error is "P2025".

/**
 * @deprecated please don´t rely on type checks to this error anymore.
 * This will become a PrismaClientKnownRequestError with code P2025
 * in the future major version of the client
 */
export declare class NotFoundError extends PrismaClientKnownRequestError {
    constructor(message: string);
}