Open kratoon opened 4 years ago
I have the same error using
serverProcess = crossSpawn('node', [
someScriptFullPath,
'--port', serverPort,
], {
stdio: [null, null, null, 'ipc'],
});
on node 16, with nodist
I believe (in my case), that nodist is the culprit because the shim is in go, and docs says
Accessing the IPC channel fd in any way other than process.send() or using the IPC channel with a child process that is not a Node.js instance is not supported.
so it probably breaks here.
a workaround is to use fork
which does not use the shim
Stack trace:
Hey guys, I have a problem with child_process on windows while using ipc so I asked a question.
I found this module to solve it but the same error happens.
The problem occurs on windows, spawning something in js (e.g. npm or child.js) and with ipc option. The ipc is required as some of the commands will be my commands and I need to communicate with it.
I am not sure what I am doing wrong. Thanks for help.
Code:
Stack trace: