title: npm ERR! EPROTO: protocol error, symlink '../@babel/parser/bin/babel-parser.js' -> '/home/vagrant/code/proadco.test/node_modules/.bin/parser'
body: <p>I'm attempting to execute <code>npm install</code> in Git Bash client on Windows 8.1 but receiving the following error:</p>
  
  <pre><code>npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/fsevents):
  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: minimist@1.2.0 (node_modules/fsevents/node_modules/rc/node_modules/minimist):
  npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, open '/home/vagrant/code/proadco.test/node_modules/fsevents/node_modules/rc/node_modules/minimist/package.json.737544774'
  
  npm ERR! path ../@babel/parser/bin/babel-parser.js
  npm ERR! code EPROTO
  npm ERR! errno -71
  npm ERR! syscall symlink
  npm ERR! EPROTO: protocol error, symlink '../@babel/parser/bin/babel-parser.js' -&gt; '/home/vagrant/code/mysite.test/node_modules/.bin/parser'
  
  npm ERR! A complete log of this run can be found in:
  npm ERR!     /home/vagrant/.npm/_logs/2019-06-24T02_39_32_641Z-debug.log
  </code></pre>
  
  <p>Running <code>npm install --no-bin-links</code> allows it to run successfully. But I don't full understand the consequences of this action. I believe it's saying "Don't create a symlink. Which is just a hack instead of resolving the root of the issue. But I've read that Windows doesn't support symlinks so it's impossible to solve.</p>
  
  <p>Can someone explain what the consequences here are? And possibly how to overcome the root issue of symlinks?</p>