Why does Node.js v4.0.0 complain about child_process execSync because of Supervisord?

Question

linux

Why does Node.js v4.0.0 complain about child_process execSync when this method was added back in 0.1.1+? What is the strangest thing on the Win machine, everything works fine, but Linux Centos swears like it is

Missing error handler on `socket`.
TypeError: Object #<Object> has no method 'execSync'
    at _diskSpace (/apps/server.ru/node_modules/fd-diskspace/bin/index.js:139:32)
    at Object.diskSpaceSync (/apps/server.ru/node_modules/fd-diskspace/bin/index.js:171:10)
    ...

UPD:
I noticed that if you run the application not through Supervisord, but simply through node app.js , everything works fine, but this is not an output.
UPD 2:
It turns out that supervisord starts node v0.10.36, although if you enter npde -v in SLI, it will say v4 .0.0