Задачи yii и react
Необходимо разобраться почему не билдиться проект.Предположительно проблема с версией npmстек технологий, на котором написан проектback - yii2front - react (next js)Логи0 info it worked if it ends with ok1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]2 info using [email protected] info using [email protected] verbose run-script [ 'prebuild', 'build', 'postbuild' ]5 info lifecycle rgbrands@~prebuild: rgbrands@6 info lifecycle rgbrands@~build: rgbrands@7 verbose lifecycle rgbrands@~build: unsafe-perm in lifecycle true8 verbose lifecycle rgbrands@~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/rg-brands.com/front/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin9 verbose lifecycle rgbrands@~build: CWD: /var/www/rg-brands.com/front10 silly lifecycle rgbrands@~build: Args: [ '-c', 'next build' ]11 silly lifecycle rgbrands@~build: Returned: code: 1 signal: null12 info lifecycle rgbrands@~build: Failed to exec build script13 verbose stack Error: rgbrands@ build: next build13 verbose stack Exit status 113 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)13 verbose stack at EventEmitter.emit (events.js:223:5)13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)13 verbose stack at ChildProcess.emit (events.js:223:5)13 verbose stack at maybeClose (internal/child_process.js:1021:16)13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)14 verbose pkgid rgbrands@15 verbose cwd /var/www/rg-brands.com/front16 verbose Linux 4.15.0-162-generic17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"18 verbose node v12.14.119 verbose npm v6.13.420 error code ELIFECYCLE21 error errno 122 error rgbrands@ build: next build22 error Exit status 123 error Failed at the rgbrands@ build script.23 error This is probably not a problem with npm. There is likely additional logging output above.24 verbose exit [ 1, true ]