There are many options to sync folders, rsync, nfs, smb, 9p, Virtualbox or VMware native, some of these run into locking issues others don't.
I think the problem in your case may not be fully understanding why doing `npm install` in a synced location is a terrible idea. If your host operating system is Windows, it doesn't understand symlinks very well, and many of the shared/synced folder methods don't like them either, but npm uses symlinks heavily unless it detects that it is running on Windows, which it can't do when it is inside a VM. For any projects requiring npm I almost always have better luck copying from /vagrant/my-project to /home/vagrant/my-project and then doing development and either pushing to version control from the copied location or manually copying back to the shared folder (and ignoring unnecessary files in the copy using the gitignore to greatly speed things up). -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/79747ecf-f939-44e9-862a-f35fd702330b%40googlegroups.com.
