Killing a child process returns exit code 0 instead of null

[SamVerschueren]

Environment details

• OS: macOS Big Sur
• OS version: 11.1
• node-pty version: 0.10.0

Issue description

I'm testing some things out with node-pty and noticed a difference between how Node.js child_process handles on exit and how node-pty handles them.

I wrote a small example.

child.js

Just a small program that logs tick every second.

setInterval(() => {
    console.log('tick');
}, 1000);

cp.js

const cp = require('child_process');

const child = cp.spawn('node', ['child.js']);

child.on('exit', (exitCode, signal) => {
    console.log(exitCode, signal);
});

child.kill('SIGINT');

When I run this code, it logs

null SIGINT

So, the exitCode is null here because it was killed with a signal like SIGINT.

pty.js

const pty = require('node-pty');

const child = pty.spawn('node', ['./child.js']);

child.onExit(({exitCode, signal}) => {
    console.log(exitCode, signal);
});

child.kill('SIGINT');

Doing the same with node-pty however, gives me the following result

0 2

2 is the numeric value of SIGINT, but the exit code is 0 indicating that the process exited just fine.

The same goes if the child.js kills itself with process.exit(1) for instance, the signal with child_process is null, but for node-pty it's 0.

I'm wondering if node-pty wants to be on par with how child_process works or if this is expected behaviour?

Thanks for the package though, it's awesome :)!

[Tyriar]

I think we just pass along the code and signal, so not sure why this is happening:

node-pty/src/unix/pty.cc

Lines 505 to 508 in 6cf84b7

	v8::Local<v8::Value> argv[] = {
	Nan::New<v8::Integer>(baton->exit_code),
	Nan::New<v8::Integer>(baton->signal_code),
	};

node-pty/src/unixTerminal.ts

Line 78 in 6cf84b7

const onexit = (code: number, signal: number): void => {

[Tyriar]

We should probably align here and hardcode null as the code when kill is called.