VirtualBox shared folders had their own problems. `npm` wants to create symlinks for commands provided by packages, but VirtualBox doesn't support symlinks by default on Windows shares. So you have to execute an arcane command to enable that feature -- every time you restart the computer.
Interesting to hear that performance is decent with the Samba share. I presumed it would be otherwise. In that case, Hyper-V with Samba may be my last shot at getting the machine to work for me... we'll see if I can muster any more enthusiasm.
[EDIT: Also, reading GP, it looks like their issue is something about VirtualBox support for symlinks, not Windows support for symlinks. Symlinks are enabled in Windows by default, so they'd only have to do something special if they were on a domain that disabled them in the group policy--but in that case, they wouldn't be able to turn them back on themselves on a reboot anyway.]
Re. Hyper-V: yeah, I do a Samba mount. This in my experience actually performs a ton better than VirtualBox shared folders, but it's been a long time. I have no idea how it compares to VMware's implementation. (VMware and VirtualBox also have the ability to cleanly virtualize a graphics-accelerated Linux desktop, which is not something I need or care about, but might be a show-stopper for both WSL and Hyper-V if you do.)