gulp --production error

[wudustan]

Hi, I am getting this error

####@SKATHI:/etc/not-gwent-online$ sudo npm run build

[email protected] build /etc/not-gwent-online gulp --production

[16:47:57] Using gulpfile /etc/not-gwent-online/gulpfile.js [16:47:57] Starting 'watch'... [16:47:57] Finished 'watch' after 167 μs [16:47:57] Starting 'browserify'... [16:47:57] Finished 'browserify' after 28 ms [16:47:57] Starting 'sass'... [16:47:57] Finished 'sass' after 11 ms [16:47:57] Starting 'unit tests'... [16:47:57] Finished 'unit tests' after 6.98 ms [16:47:57] Starting 'index'... [16:47:57] Finished 'index' after 3.26 ms [16:47:57] Starting 'resize sm'... [16:47:57] Starting 'resize md'...

events.js:160 throw er; // Unhandled 'error' event ^ Error: Stream yields empty buffer at Socket. (/etc/not-gwent-online/node_modules/gm/lib/command.js:57:17) at emitNone (events.js:91:20) at Socket.emit (events.js:185:7) at endReadableNT (_stream_readable.js:974:12) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] build: gulp --production npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] build 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! /home/####/.npm/_logs/2017-08-22T15_47_57_980Z-debug.log

Log:

0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'run', 'build' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'prebuild', 'build', 'postbuild' ] 5 info lifecycle [email protected]~prebuild: [email protected] 6 info lifecycle [email protected]~build: [email protected] 7 verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true 8 verbose lifecycle [email protected]~build: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/etc/not-gwent-online/node_modules/.bin:/usr/lo$ 9 verbose lifecycle [email protected]~build: CWD: /etc/not-gwent-online 10 silly lifecycle [email protected]~build: Args: [ '-c', 'gulp --production' ] 11 silly lifecycle [email protected]~build: Returned: code: 1 signal: null 12 info lifecycle [email protected]~build: Failed to exec build script 13 verbose stack Error: [email protected] build: gulp --production 13 verbose stack Exit status 1 13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:289:16) 13 verbose stack at emitTwo (events.js:106:13) 13 verbose stack at EventEmitter.emit (events.js:191:7) 13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14) 13 verbose stack at emitTwo (events.js:106:13) 13 verbose stack at ChildProcess.emit (events.js:191:7) 13 verbose stack at maybeClose (internal/child_process.js:891:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) 14 verbose pkgid [email protected] 15 verbose cwd /etc/not-gwent-online 16 verbose Linux 4.8.0-36-generic 17 verbose argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build" 18 verbose node v6.11.2 19 verbose npm v5.3.0 20 error code ELIFECYCLE 21 error errno 1 22 error [email protected] build: gulp --production 22 error Exit status 1 23 error Failed at the [email protected] build script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]