Script.createContext is undefined in node 0.11.9

[chrisyip]

I noticed that node had move Script.createContext to vm.createContext (http://nodejs.org/api/vm.html#vm_vm_createcontext_initsandbox).

I wonder if it's acceptable to use something like

var createContext = Script.createContext || vm.createContext;

to make it compatible with older and newer versions of node.

[braco]

Confirming this still exists in coffee 1.8.0 with node 0.11.13

edit: @michaelficarra, sorry, but is there any plan to merge #3527 and close this issue out?

[mbrio]

Just as an update, in-case some of my other changes were causing the previous patch to not be applied, I've re-forked coffeescript with the Script.createContext fixes and requested a new pull. Hopefully this will be merged soon.

[jashkenas]

@mbrio Is there a new pull we can take a look at?

[mbrio]

@jashkenas I'll look into it right now, we've been using this fix for months now and haven't had any issues with it.

[mbrio]

@jashkenas I just submitted a PR, the browser file didn't match the output of the compiled 1.9.0 source code. When I compiled it and overwrote the browser file supplied by coffee-script-source ruby gem, the error no longer occurred.

[GeoffreyBooth]

CoffeeScript 2 supports only Node 7+. If this issue only occurs in old versions of Node, I think we can stop worrying about it. Please comment if I’m wrong and I’ll reopen.