title: ERR! code 127 when trying to use node and npm
body: <p>Started receiving an error in my Angular application last night while using the 'aws-sdk' package, something about missing 'utils'. I looked around online and saw some people recommended removing and creating a new node_modules folder with <code>npm i</code>, so that's what I did.</p>
  <p>Since then I've been unable to run any node commands, I even reinstalled node.js, and still no luck. Trying <code>npm i</code> or <code>ng generate</code> will run, create the node_modules or Angular application folder, but as it reaches the end of the install it throws me this error.</p>
  <p><a href="https://i.stack.imgur.com/a4jzb.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/a4jzb.png" alt="npm error" /></a></p>
  <p>I have a project due in a few days that I need to get this working again for, so any help is greatly appreciated. I'm really clueless as to what needs to be done.</p>
  <hr />
  <p>As someone suggested below, here is the error code.</p>
  <pre><code>PS C:\Users\lucoz\Desktop\CollegeWork\Cloud\30%\cinema-app&gt; npm i aws-sdk
  npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
  npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
  npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
  npm ERR! code 127
  npm ERR! path C:\Users\lucoz\Desktop\CollegeWork\Cloud\30%\cinema-app\node_modules\@angular\cli
  npm ERR! command failed
  npm ERR! command bash -c node ./bin/postinstall/script.js
  npm ERR! /mnt/host/c/Users/lucoz/node_modules/.bin/../node/bin/node: line 1: This: Permission denied
  
  npm ERR! A complete log of this run can be found in:
  npm ERR!     C:\Users\lucoz\AppData\Local\npm-cache\_logs\2022-04-26T15_44_14_016Z-debug-0.log
  </code></pre>
  <hr />
  <p>Fixed it! For me, I ran <code>npm cache clear --force</code>, uninstalled node.js, and reinstalled version 14.15.5 available at this link: <a href="https://nodejs.org/download/release/v14.15.5/node-v14.15.5-x64.msi" rel="nofollow noreferrer">https://nodejs.org/download/release/v14.15.5/node-v14.15.5-x64.msi</a> (note hitting this link will immediately start the download)</p>