with npm 2.0 a breaking change was introduced to how the npm scripts are handled:
this change does not add the node executable directory of the current process when executing npm scripts. some modules, like karma phantomjs launcher, rely on executing node commands as part of the post install scripts. this post install scripts will fail on machines without global node installation
fixed in 182b461
i had to refactor the way tasks are executed, instead of using CommandLine, java.lang.Process ist now used instead. this provides an option to add the current node executable to the path environment variable.