Level 6
Even tried again post package-lock.json rm -rf node_modules, npm cache clear --force and npm install to run npm run dev but I still had the same error. And logs remain vague to say the least.
Dec 8, 2020
2
Level 6
Laravel 7 Laravel Mix Error Exit status 2
Working locally on new Laravel 7 setup which is an upgrade of our Laravel 6 setup. Did a npm install post removal of node_modules directory + cache removal npm cache clear --force as well as composer install But now when I run npm run dev I get an error without much input on what the issue is at all /Users/jasper/.npm/_logs/2020-12-09T01_26_40_930Z-debug.log:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/Users/jasper/.nvm/versions/node/v14.13.0/bin/node',
1 verbose cli '/Users/jasper/.nvm/versions/node/v14.13.0/bin/npm',
1 verbose cli 'run',
1 verbose cli 'dev'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle @~predev: @
6 info lifecycle @~dev: @
7 verbose lifecycle @~dev: unsafe-perm in lifecycle true
8 verbose lifecycle @~dev: PATH: /Users/jasper/.nvm/versions/node/v14.13.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/jasper/code/domain.com/valet/node_modules/.bin:/Users/jasper/.nvm/versions/node/v14.13.0/bin:/Users/jasper/.nvm/versions/node/v9.8.0/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Apple/usr/bin:/Users/jasper/.nvm/versions/node/v9.8.0/bin:/usr/local/sbin:/Users/jasper/.composer/vendor/bin:/Users/jasper/.composer/vendor/bin
9 verbose lifecycle @~dev: CWD: /Users/jasper/code/domain.com/valet
10 silly lifecycle @~dev: Args: [ '-c', 'npm run development' ]
11 silly lifecycle @~dev: Returned: code: 2 signal: null
12 info lifecycle @~dev: Failed to exec dev script
13 verbose stack Error: @ dev: `npm run development`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter.<anonymous> (/Users/jasper/.nvm/versions/node/v14.13.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess.<anonymous> (/Users/jasper/.nvm/versions/node/v14.13.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1047:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid @
15 verbose cwd /Users/jasper/code/domain.com/valet
16 verbose Darwin 19.6.0
17 verbose argv "/Users/jasper/.nvm/versions/node/v14.13.0/bin/node" "/Users/jasper/.nvm/versions/node/v14.13.0/bin/npm" "run" "dev"
18 verbose node v14.13.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 2
22 error @ dev: `npm run development`
22 error Exit status 2
23 error Failed at the @ dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]
Any idea what the issue may be here? Seems the log is not telling me anything..
Level 6
After commented out files loaded in mix.js(...)in webpack.mix.js one by one and building with npm run dev I realized one .js file was the cause. We had added require('../assets/vendor/MediaManager/js/manager.js') there for the Laravel Media Manager. It seems it broke on that requirement. The file path is correct howeverWe are now looking into a better solution.
Please or to participate in this conversation.