Running a built binary fails with weird error

When building the Prisma 2 CLI to a binary with node-packer, I get this weird error:

❯ ./prisma-cli-darwin-2.0.0-alpha.911 version
internal/util.js:206
    throw new errors.TypeError('ERR_INVALID_ARG_TYPE', 'original', 'function');
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "original" argument must be of type function
    at promisify (internal/util.js:206:11)
    at Object.4364 (/__enclose_io_memfs__/build/index.js:2:1368472)
    at __webpack_require__ (/__enclose_io_memfs__/build/index.js:2:154)
    at Object.2740 (/__enclose_io_memfs__/build/index.js:2:706082)
    at __webpack_require__ (/__enclose_io_memfs__/build/index.js:2:154)
    at Object.5575 (/__enclose_io_memfs__/build/index.js:2:1677696)
    at __webpack_require__ (/__enclose_io_memfs__/build/index.js:2:154)
    at Object.729 (/__enclose_io_memfs__/build/index.js:2:142604)
    at __webpack_require__ (/__enclose_io_memfs__/build/index.js:2:154)
    at Object.6292 (/__enclose_io_memfs__/build/index.js:2:1880810)

I’m not quite sure why this happens, but it may have something to do with either 1) Promises (due to the error message) or 2) the file system (due to the fact that these bundlers use a virtual file system); but I’m also not sure if it has to do anything with either of those.

It happens in the latest alpha (tested with 2.0.0-alpha.1000), and I could track it back to 2.0.0-alpha.911, it did not not happen before 2.0.0-alpha.911.

[timsuchanek]

This can now be accomplished with pkg and the following steps:

mkdir build
cd build
yarn init -y
npm i -g pkg
yarn add @prisma/cli@alpha
cd node_modules/@prisma/cli
pkg .
./cli-macos --version

[pantharshit00]

@adrianoresende Prisma won’t run on frontend. Please make sure you are running Prisma in node