Anybody managed to do a successful Zeit Deployment. With Zeit 2.0 I am getting many build problems. Help is appreciated.
Fetched deployment "18nbjiu45.now.sh" in nottinhill [1s]
2019-09-16T20:41:05.389Z installing build runtime...
2019-09-16T20:41:05.394Z yarn info @now/build-utils@latest...
2019-09-16T20:41:05.399Z yarn info @now/static-build...
2019-09-16T20:41:06.249Z build runtime installed: 860.593ms
2019-09-16T20:41:06.866Z obtaining caches...
2019-09-16T20:41:07.782Z running builder.exports.build...
2019-09-16T20:41:07.783Z Downloading user files...
2019-09-16T20:41:07.790Z installing to /tmp/2d0a8bef
2019-09-16T20:41:39.213Z
2019-09-16T20:41:39.213Z > dtrace-provider@0.8.7 install /tmp/2d0a8bef/node_modules/dtrace-provider
2019-09-16T20:41:39.213Z > node-gyp rebuild || node suppress-error.js
2019-09-16T20:41:39.213Z
2019-09-16T20:41:40.840Z make: Entering directory `/tmp/2d0a8bef/node_modules/dtrace-provider/build'
2019-09-16T20:41:40.841Z TOUCH Release/obj.target/DTraceProviderStub.stamp
2019-09-16T20:41:40.846Z make: Leaving directory `/tmp/2d0a8bef/node_modules/dtrace-provider/build'
2019-09-16T20:41:40.920Z
2019-09-16T20:41:40.920Z > sqlite3@4.0.9 install /tmp/2d0a8bef/node_modules/ghost/node_modules/sqlite3
2019-09-16T20:41:40.920Z > node-pre-gyp install --fallback-to-build
2019-09-16T20:41:40.920Z
2019-09-16T20:41:41.223Z node-pre-gyp
2019-09-16T20:41:41.224Z
2019-09-16T20:41:41.224Z WARN Using request for node-pre-gyp https download
2019-09-16T20:41:41.880Z [sqlite3] Success: "/tmp/2d0a8bef/node_modules/ghost/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node" is installed via remote
2019-09-16T20:41:41.889Z
2019-09-16T20:41:41.889Z > sharp@0.23.0 install /tmp/2d0a8bef/node_modules/sharp
2019-09-16T20:41:41.889Z > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
2019-09-16T20:41:41.889Z
2019-09-16T20:41:42.184Z info
2019-09-16T20:41:42.185Z
2019-09-16T20:41:42.185Z sharp
2019-09-16T20:41:42.186Z Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.8.1/libvips-8.8.1-linux-x64.tar.gz
2019-09-16T20:41:45.680Z
2019-09-16T20:41:45.680Z > core-js@2.6.9 postinstall /tmp/2d0a8bef/node_modules/@babel/polyfill/node_modules/core-js
2019-09-16T20:41:45.680Z > node scripts/postinstall || echo "ignore"
2019-09-16T20:41:45.680Z
2019-09-16T20:41:45.768Z Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
2019-09-16T20:41:45.768Z
2019-09-16T20:41:45.769Z The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
2019-09-16T20:41:45.769Z > https://opencollective.com/core-js
2019-09-16T20:41:45.770Z > https://www.patreon.com/zloirock
2019-09-16T20:41:45.770Z
2019-09-16T20:41:45.770Z Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
2019-09-16T20:41:45.770Z
2019-09-16T20:41:45.886Z
2019-09-16T20:41:45.886Z > jsonpath@1.0.2 postinstall /tmp/2d0a8bef/node_modules/ghost/node_modules/jsonpath
2019-09-16T20:41:45.886Z > node lib/aesprim.js > generated/aesprim-browser.js
2019-09-16T20:41:45.886Z
2019-09-16T20:41:46.943Z npm WARN bookshelf@0.14.2 requires a peer of knex@>=0.6.10 <0.15.0 but none is installed. You must install peer dependencies yourself.
2019-09-16T20:41:46.943Z npm WARN ghost@1.0.0 No repository field.
2019-09-16T20:41:46.943Z
2019-09-16T20:41:46.948Z added 1054 packages from 748 contributors and audited 9267 packages in 38.528s
2019-09-16T20:41:46.949Z found 107 vulnerabilities (19 moderate, 88 high)
2019-09-16T20:41:46.949Z run `npm audit fix` to fix them, or `npm audit` for details
2019-09-16T20:41:46.972Z Running "build" script in "package.json"
2019-09-16T20:41:46.973Z running "npm run build"
2019-09-16T20:41:47.289Z
2019-09-16T20:41:47.289Z > ghost@1.0.0 build /tmp/2d0a8bef
2019-09-16T20:41:47.289Z > next build
2019-09-16T20:41:47.289Z
2019-09-16T20:41:47.294Z sh: next: command not found
2019-09-16T20:41:47.296Z npm
2019-09-16T20:41:47.297Z ERR! file
2019-09-16T20:41:47.297Z sh
2019-09-16T20:41:47.297Z npm
2019-09-16T20:41:47.297Z ERR! code ELIFECYCLE
2019-09-16T20:41:47.297Z npm ERR! errno ENOENT
2019-09-16T20:41:47.297Z npm ERR!
2019-09-16T20:41:47.297Z syscall spawn
2019-09-16T20:41:47.298Z npm
2019-09-16T20:41:47.299Z ERR! ghost@1.0.0 build: `next build`
2019-09-16T20:41:47.299Z npm
2019-09-16T20:41:47.299Z ERR! spawn ENOENT
2019-09-16T20:41:47.299Z npm ERR!
2019-09-16T20:41:47.299Z
2019-09-16T20:41:47.299Z npm ERR!
2019-09-16T20:41:47.299Z Failed at the ghost@1.0.0 build script.
2019-09-16T20:41:47.299Z npm ERR!
2019-09-16T20:41:47.299Z This is probably not a problem with npm. There is likely additional logging output above.
2019-09-16T20:41:47.305Z
2019-09-16T20:41:47.305Z npm ERR! A complete log of this run can be found in:
2019-09-16T20:41:47.305Z npm ERR!
2019-09-16T20:41:47.305Z /tmp/.npm/_logs/2019-09-16T20_41_47_300Z-debug.log
2019-09-16T20:41:47.312Z Error: Exited with 1
2019-09-16T20:41:47.312Z at ChildProcess.child.on (/tmp/41d02aa0e2a0c97f/.build-utils/.builder/node_modules/@now/static-build/dist/index.js:23427:24)
2019-09-16T20:41:47.312Z at emitTwo (events.js:126:13)
2019-09-16T20:41:47.312Z at ChildProcess.emit (events.js:214:7)
2019-09-16T20:41:47.312Z at maybeClose (internal/child_process.js:925:16)
2019-09-16T20:41:47.312Z at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
2019-09-16T20:41:47.378Z worker exited with code 20 and signal null
2019-09-16T20:41:47.386Z done
2019-09-16T20:41:49.897Z done