title: Problems running npm install on Elastic Beanstalck
body: <h2>Situation</h2>
  
  <p>I have a Laravel (5.4) application that uses npm, bower and gulp for frontend.</p>
  
  <p>I have configured all with success on deploy but the <code>npm install</code> or <code>npm install --production</code> (that in my case is the same) command give me errors and makes the deploy to fail. </p>
  
  <h2>Problem</h2>
  
  <p>Here is the "Causes" as response from AWS when i run <code>eb deploy</code> command.</p>
  
  <pre><code>Application update failed at 2017-06-07T17:08:38Z with exit status 1 and error: container_command 01-npm-install in .ebextensions/05-frontend-install.config failed.
  
  npm WARN lifecycle npm is using /usr/bin/node but there is no node binary in the current PATH. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
  npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
  npm WARN deprecated minimatch@1.0.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
  npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
  npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
  npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases &gt;= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
  npm WARN prefer global node-gyp@3.6.2 should be installed with -g
  npm WARN prefer global marked@0.3.6 should be installed with -g
  
  &gt; node-sass@3.13.1 install /var/app/ondeck/node_modules/node-sass
  &gt; node scripts/install.js
  
  npm ERR! file sh
  npm ERR! path sh
  npm ERR! code ELIFECYCLE
  npm ERR! errno ENOENT
  npm ERR! syscall spawn sh
  npm ERR! node-sass@3.13.1 install: `node scripts/install.js`
  npm ERR! spawn sh ENOENT
  npm ERR!
  npm ERR! Failed at the node-sass@3.13.1 install script.
  npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  
  npm ERR! A complete log of this run can be found in:
  npm ERR! /root/.npm/_logs/2017-06-07T17_08_38_740Z-debug.log.
  Incorrect application version "app-5d9c-170607_190633" (deployment 40). Expected version "app-0466-170606_110037" (deployment 31).
  </code></pre>
  
  <p>The <code>.ebextensions/05-frontend-install.config</code> file has this content</p>
  
  <pre><code>container_commands:
    00-npm-upgrade:
      command: "npm install -g npm@latest"
    01-npm-install:
      command: "npm install --production"
    02-gulp-install:
      command: "sudo npm install gulp"
    03-bower-install:
      command: "sudo npm install bower"
    04-bower-deploy:
      command: "sudo bower install --allow-root"
    05-gulp-deploy:
      command: "sudo npm run prod"
  </code></pre>