Commits on Oct 9, 2019

1. chore: reduce concurrency to avoid bootstrap issues due to npm locks …

   It happens very frequently for me with `npm run update-packages`, which
   is also part of our release process.
   
   Sample error:
   
   lerna ERR! npm install exited 254 in '@loopback/service-proxy'
   lerna ERR! npm install stderr:
   npm ERR! code ENOENT
   npm ERR! syscall lchown
   npm ERR! path /Users/rfeng/.npm/_locks/staging-1f9c9b6dc2a3f888.lock
   npm ERR! errno -2
   npm ERR! enoent ENOENT: no such file or directory, lchown '/Users/rfeng/.npm/_locks/staging-1f9c9b6dc2a3f888.lock'
   npm ERR! enoent This is related to npm not being able to find a file.
   npm ERR! enoent

   

   raymondfeng committed Oct 9, 2019
   Configuration menu

   • View commit details
   • Copy full SHA for 1d50a97
   • Browse repository at this point

   Copy the full SHA

   1d50a97 View commit details

   Browse the repository at this point in the history