Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error classes are wrapped twice #7035

Closed
janpio opened this issue May 11, 2021 · 2 comments · Fixed by #8965
Closed

Error classes are wrapped twice #7035

janpio opened this issue May 11, 2021 · 2 comments · Fixed by #8965

Comments

@janpio
Copy link
Member

janpio commented May 11, 2021

Client error messages always include the exception type twice, one with an added 2 at the end:

PrismaClientInitializationError2 [PrismaClientInitializationError]: 
Invalid `prisma.user.create()` invocation:
...

This does not seem to be intended and should be fixed.

Internal discussion: https://prisma-company.slack.com/archives/C016KUHB1R6/p1620728621001000

That comes from esbuild
It means that we’re for whatever reason probably bundling the runtime twice
So someone would need to debug the esbuild output

@janpio
Copy link
Member Author

janpio commented Aug 25, 2021

This got worse along the way, we are now up to PrismaClientInitializationError3 (see #8836)

@janpio
Copy link
Member Author

janpio commented Aug 27, 2021

Also effects other error types now: PrismaClientKnownRequestError3 [PrismaClientKnownRequestError] (via #8839 (comment))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants