Typo

.gitlab-ci.yml

@@ -109,7 +109,7 @@ update(metager3.de):
     - chmod -R 777 storage
     - chmod -R 777 bootstrap/cache
     - npm install
-    - npm run prodution
+    - npm run production
     - php artisan migrate --force
     - if [ -f ~/MetaGer/artisan ]; then php ~/MetaGer/artisan down;fi
     - cd ~/

npm-debug.log

+0 info it worked if it ends with ok
+1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
+1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
+1 verbose cli   'run',
+1 verbose cli   'production' ]
+2 info using npm@3.10.10
+3 info using node@v6.10.3
+4 verbose run-script [ 'preproduction', 'production', 'postproduction' ]
+5 info lifecycle @~preproduction: @
+6 silly lifecycle @~preproduction: no script for preproduction, continuing
+7 info lifecycle @~production: @
+8 verbose lifecycle @~production: unsafe-perm in lifecycle true
+9 verbose lifecycle @~production: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\SumaEV\MetaGer\node_modules\.bin;C:\ProgramData\Oracle\Java\javapath;C:\PHP7;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\ProgramData\ComposerSetup\bin;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Program Files\Redis;C:\Windows\System32;C:\WINDOWS\system32;C:\Users\SumaEV\Downloads\platform-tools;C:\Users\SumaEV\AppData\Local\Microsoft\WindowsApps;C:\Users\SumaEV\AppData\Roaming\Composer\vendor\bin;C:\Users\SumaEV\AppData\Roaming\npm;C:\Programme\Java\jdk1.8.0_131\bin;C:\Program Files (x86)\Nmap;;C:\Program Files\Microsoft VS Code\bin
+10 verbose lifecycle @~production: CWD: C:\Users\SumaEV\MetaGer
+11 silly lifecycle @~production: Args: [ '/d /s /c',
+11 silly lifecycle   'cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js' ]
+12 silly lifecycle @~production: Returned: code: 1  signal: null
+13 info lifecycle @~production: Failed to exec production script
+14 verbose stack Error: @ production: `cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
+14 verbose stack Exit status 1
+14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
+14 verbose stack     at emitTwo (events.js:106:13)
+14 verbose stack     at EventEmitter.emit (events.js:191:7)
+14 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
+14 verbose stack     at emitTwo (events.js:106:13)
+14 verbose stack     at ChildProcess.emit (events.js:191:7)
+14 verbose stack     at maybeClose (internal/child_process.js:886:16)
+14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
+15 verbose pkgid @
+16 verbose cwd C:\Users\SumaEV\MetaGer
+17 error Windows_NT 10.0.16299
+18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "production"
+19 error node v6.10.3
+20 error npm  v3.10.10
+21 error code ELIFECYCLE
+22 error @ production: `cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
+22 error Exit status 1
+23 error Failed at the @ production script 'cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
+23 error Make sure you have the latest version of node.js and npm installed.
+23 error If you do, this is most likely a problem with the  package,
+23 error not with npm itself.
+23 error Tell the author that this fails on your system:
+23 error     cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
+23 error You can get information on how to open an issue for this project with:
+23 error     npm bugs
+23 error Or if that isn't available, you can get their info via:
+23 error     npm owner ls
+23 error There is likely additional logging output above.
+24 verbose exit [ 1, true ]