Error when running npm run dev on laravel + inertia + linux

Question

0 The message is valid if it ends with ok 1 Details cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev' ] 2 Information about using npm@6.14.4 3 Information about using node@v10.19.0 4 Detailed running script [ 'predev', 'dev', 'postdev' ] 5 Information life cycle @~predev: @ 6 Information life cycle @~dev: @ 7 verbose lifecycle @~dev:lifecycle true 8 unsafe-perm in verbose lifecycle @~dev: path: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/SostLaravel/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/ sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/mssql-tools18/bin 9 Detailed life cycle @~dev: CWD: /var/www/html/SostLaravel 10 Stupid Lifecycle @~dev: Args: [ '-c', 'npm rundevelopment' ] 11 Stupid lifetime@~dev: return: code: 1 signal: null 12 message lifetime @~dev: Unable to execute development script 13 verbose stack error: @dev: npm rundevelopment 13 verbose stack exit status 1 13 verbose stack

That event emitter. (/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16) 13 Details stack that event emitter. emit (events.js:198:13) 13 verbose stack

in the child process. (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack in child process. emit (events.js:198:13) 13 verbose The stack is located at MaybeClose (internal/child_process.js:982:16) 13 Details Stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 14 verbose pkgid @ 15 verbose cwd /var/www/html/SostLaravel 16 Details Linux 5.4.0-135-generic 17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "dev" 18 verbose node v10.19.0 19 verbose npm v6.14.4 20 error code ELIFECYCLE 21 error errno 1 22 error @ dev: npm rundevelopment 22 error exit Status 1 23 Error @dev script failed. 23 Error This is Probably not npm's problem. There may be additional logging The output is as above. 24 Verbose exit [ 1, true ]

Good morning, I've cleared the cache, I've reinstalled npm, I've removed the node modules and package locks, I've done everything but everything results in the same error.

Answer 1

It might be a good idea to check your node version and make sure it's compatible with your packages.