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.

vercel/pkg errors on windows

See original GitHub issue

NOTE: This is a “draft issue”, so it may not be actionable at this time. See below for more info.

Bug description

+ ./cli.exe --version
Error: Command failed with ENOENT: D:\snapshot\node_modules\@prisma\cli\introspection-engine-windows.exe --version
spawn D:\snapshot\node_modules\@prisma\cli\introspection-engine-windows.exe ENOENT

How to reproduce

NOTE: This only happens on GitHub Actions right now. NOTE: I don’t know when this bug was introduced yet, because of another bug.

npm i @prisma/cli
npm i -g pkg
pkg node_modules/@prisma/cli -t node12-win
./cli.exe version

Also see https://github.com/prisma/e2e-tests/runs/1092141690

Expected behavior

no error

Prisma information

–

Environment & setup

–

Issue Analytics

State:
Created 3 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

steebchencommented, Oct 27, 2020

This is the reason I’m using pkg currently, since it just magically picks up everything without any extra steps needed and just works (well, except for this specific issue, but it looks like a specific commit in @prisma/cli broke the built binary on windows). The command is really just pkg node_modules/@prisma/cli and that’s it.

0reactions

yoshuawuytscommented, Oct 27, 2020

Ah yeah, it seems you need to use a bundler to concat it into a single file before running boxed node. There should be ways of including a binary through this as well, but then this probably needs a build matrix too. Thinking this through this def sounds trickier than expected, but is probably a requirement for all single-binary creations.