Cloning service-template-node into home dir in vagrant and doing npm install && npm start works fine, but doing the same in vagrant's /vagrant dir that has been mapped to the windows host's drive and doing npm install --no-bin-links && npm start gives this error.
I tracked it down to using the "--no-bin-links" flag - seems like the service-running fails with that option.
vagrant@mediawiki-vagrant:/vagrant/service-template-node$ npm start > service-template-node@0.0.0 start /vagrant/service-template-node > service-runner sh: 1: service-runner: not found npm ERR! service-template-node@0.0.0 start: `service-runner` npm ERR! Exit status 127 npm ERR! npm ERR! Failed at the service-template-node@0.0.0 start script. npm ERR! This is most likely a problem with the service-template-node package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! service-runner npm ERR! You can get their info via: npm ERR! npm owner ls service-template-node npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.13.0-30-generic npm ERR! command "/usr/bin/node" "/usr/bin/npm" "start" npm ERR! cwd /vagrant/service-template-node npm ERR! node -v v0.10.36 npm ERR! npm -v 1.4.28 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /vagrant/service-template-node/npm-debug.log npm ERR! not ok code 0