T89919: Services in Vagrant should not be cloned into root moved Node.JS service repos into /vagrant/srv, which causes node module installs to fail on Windows hosts. The root cause are symlinks created by npm for certain modules.
Options:
- Symlinks become available when Vagrant is run with admin rights, so list that as a workaround on the MW-Vagrant page.
- Use npm install --no-bin-links and then try to work around various issues that might arise for each service.
- Move them out of /vagrant and bikeshed yet again on where to actually put them
I'm strongly in favour of option 1 as it affects only Windows users that install services.
First reported in T90353 , recently appeared in https://gerrit.wikimedia.org/r/#/c/211957/2/puppet/modules/mathoid/manifests/install/git.pp