Prisma hangs when javascript is minified

Bug description

We noticed that if code is bundled and prisma throws a constraint error (e.g. duplicate key on insert, or invalid foreign key) the execution hangs.

How to reproduce

Implement code that would cause prisma to throw a constraint error. If executed, the exception is properly raise. Now bundle the code with a bundler (e.g. esbuild). Execute again and notice that the application hangs.

Expected behavior

The bundled code should throw the expected exception

Prisma information

The issue seems to be unrelated to the schema. Just need a couple of tables with a FK constraint.

Environment & setup

• OS: AWS Lambda (Amazon Linux 2)
• Database: PostgreSQL
• Node.js version: 14

Prisma Version

prisma                  : 3.10.0
@prisma/client          : 3.10.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : 73e60b76d394f8d37d8ebd1f8918c79029f0db86
Studio                  : 0.458.0

[mdesousa]

hi @janpio , please take a look at this repository: https://github.com/holasivo/prisma-12355 in testing with this simple repo, the code actually works… but it is very slow when minified i’m wondering now if the issue is related to the exception including the source code. trying to print that may be a lot slower for minified code (there are no line breaks, the file is larger, etc.). our application has a lot more code getting minified and it times out after 30 seconds. i’d also recommend to avoid printing source code in the exception message for security reasons… the stack trace already provides the code context. thanks!

[millsp]

Because we need to find the schema and the engine in order to run the queries, we have logic to find that but it is suboptimal.