spawning a coffee child process doesn't work as expected

[paulpflug]

I have two files

test.coffee

spawn = require('child_process').spawn
child = spawn("coffee",["subtest.coffee"])
child.stdout.on 'data', (data) -> 
  console.log('stdout: ' + data)
console.log(child.pid)

and
subtest.coffee

console.log(process.pid)

Output when running coffee test.coffee

6596
stdout: 6436

The pids should match..
So coffee makes its own child process?
The problem is, that the child process cannot be killed..
See here
and here

[paulpflug]

could be windows specific..

[MetaMemoryT]

I am also running on windows, what could be a work around to kill the coffee child process?

The child process is created here in forkNode:
https://github.com/jashkenas/coffeescript/blob/master/src/command.coffee

[paulpflug]

The only workaround I know is to call
node {{path-to-coffee}} script.coffee
instead of
coffee script.coffee

this will give the right child id

[akre54]

node $(which coffee) script.coffee on bash.

[vendethiel]

@akre54 Are you experiencing this problem on non-windows ?

[akre54]

Nope, just pointing out a nice one-liner to the above :)

[vendethiel]

Yeah, but that's a windows-specific problem, so it probably won't be that useful :)

[akre54]

Yeah, there's an equivalent in powershell (lemme look it up, was on an older gulp thread).

EDIT: http://stackoverflow.com/questions/304319/is-there-an-equivalent-of-which-on-the-windows-command-line

[GeoffreyBooth]

The coffee command is intended primarily for compiling and secondarily for debugging, not as a replacement for the node command that is intended to run code.