Prisma 4.3.1 distribution is bundling a libquery_engine

[mwillbanks]

Bug description

The prisma distribution is bundling the debian libquery engine which results in larger runtime builds and can cause issues when deploying to lambda via zip.

ls node_modules/@prisma/internals/dist/libquery_engine-*                                                                                                                                
node_modules/@prisma/internals/dist/libquery_engine-debian-openssl-1.1.x.so.node

How to reproduce

1. yarn add @prisma/client or npm install @prisma/client
2. ls node_modules/@prisma/internals/dist/libquery_engine-*

Expected behavior

The libquery_engine for debian or any OS for that matter would not be within the internals/dist.

Prisma information

Not relevant.

Environment & setup

• OS: macOS
• Database: PostgreSQL
• Node.js version: v16.17.0

Prisma Version

Environment variables loaded from .env
prisma                  : 4.3.1
@prisma/client          : 4.3.1
Current platform        : darwin
Query Engine (Node-API) : libquery-engine c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt c875e43600dfe042452e0b868f7a48b817b9640b (at node_modules/@prisma/engines/prisma-fmt-darwin)
Format Wasm             : @prisma/prisma-fmt-wasm 4.3.0-32.c875e43600dfe042452e0b868f7a48b817b9640b
Default Engines Hash    : c875e43600dfe042452e0b868f7a48b817b9640b
Studio                  : 0.473.0

[millsp]

Hey @mwillbanks, we are aware that is this an issue, but you should not get @prisma/internals installed via @prisma/client or prisma. Can you please double check that you did not include @prisma/internals in your dependencies or via a third-party dependency (eg. a prisma generator, etc...)?

[mwillbanks]

So this is getting included on my side unfortunately because we have typegraphql-prisma as a dependency which should have been a dev-dependency. so you are correct in that it is being hoisted from something else.

[millsp]

Awesome. I will keep this issue around for us to actually stop publishing engines too. Thanks!

[Jolg42]

@mwillbanks Thanks for this issue, I created and merged a PR about this 🙌🏼

@prisma/internals unpacked package went from 124.4 MB to 395.4 kB 😅

After Prisma version 4.8.0 is released (December 20th) you will have to wait for it to be bumped in a new version of typegraphql-prisma I think.