Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Packaged CLI cannot be used to generate the JS client

See original GitHub issue

Bug description

If the CLI is packaged into a single binary using pkg then it cannot be used to generate the JS client.

How to reproduce

https://github.com/RobertCraigie/prisma-pkg-reproduction

Expected behavior

The Client should be correctly generated.

Prisma information

N/A

Environment & setup

OS: Mac OS
Database: N/A/
Node.js version: v17.1.0

Prisma Version

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

Additional Context

The packaged CLI is currently being used by prisma-client-go and https://github.com/RobertCraigie/prisma-client-py

Issue Analytics

State:
Created 2 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

janpiocommented, Dec 4, 2021

Aha, so my reproduction is getting the same right now - which seems to be the “figure out the command to run this generator to make it generate” code which is then used here https://github.com/prisma/prisma/blob/bbdf1c23653a77b0b5bf7d62efd243dcebea018b/packages/generator-helper/src/GeneratorProcess.ts#L45-L51

Seems by hand coding the provider path you are effectively skipping over that small problem already and are allowing it to succeed further. Interesting.

1reaction

janpiocommented, Dec 3, 2021

Unfortunately lives in a non obvious location: https://github.com/prisma/engines-wrapper/blob/7195c6e751d3661cfc5df1e1126789b88c291494/packages/engines/src/index.ts#L17-L25 (Quite a smell that this logic is in 2 different repos although closely related)