Hello,
i would like to cross-pkg an app from MacOS for Windows. In the app i'm using pino as logging module. When i start the app on CMD, the app opens up and closes silently with no log output at all.
I've made a sandbox script:
const pino = require()'pino'
console.log('Setting up pino ...')
const log = pino({ level: 'debug', name: 'main' })
log.info('Initializing...')
process.on('error', err => console.error(err))
This command i use to pkg:
pkg -t node10-win-x64 -o ./pkg_test_win package.json
Pkging the same script on windows, it works fine.
Am i doing something wrong?
Greetz and thanks in advance,
Christian
I have the same problem when trying to use commander.js. When cross-packaging a simple commander.js app from macOS to Windows binaries, I get no output. When packaging from Windows to Windows binaries, everything works.
Coincidentally I just noticed today that my issue #686 also applies on macOS, so the two are duplicate/related :)
My issue is cross-packaging from Linux to macOS/Windows
For now I've reverted to pkg 4.3.8 which seems to work fine.
Thank you for the tip @AxelTerizaki! Reverting to 4.3.8 helped me as well.
We were having issues building from Windows to Linux and Reverting to 4.3.8 solved our issues too.
Is it still happening here too with 4.4.2 ? This version solved my similar issue.
Can we setup github actions for testing this behavior? It is possible to run OS X, Unix and Windows actions 馃
Afaik this issue is still present in 4.4.x
Most helpful comment
Coincidentally I just noticed today that my issue #686 also applies on macOS, so the two are duplicate/related :)
My issue is cross-packaging from Linux to macOS/Windows
For now I've reverted to pkg 4.3.8 which seems to work fine.