-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm success ,however npm start fail #83
Comments
Hi, I encountered same issues. Did you solve it or you used alternative way |
Same problem. After a few fixes, the npm install went fine, but npm start drew this error. $ cat /home/pi/.npm/_logs/2022-11-24T21_50_19_165Z-debug.log Running Debian Bullseye on pi4/8G |
Try a different version of pi is
…On Thu, Nov 24, 2022 at 4:53 PM JamesCHub ***@***.***> wrote:
Same problem. After a few fixes, the npm install went fine, but npm start
drew this error.
$ cat /home/pi/.npm/_logs/2022-11-24T21_50_19_165Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using ***@***.***
3 info using ***@***.***
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle ***@***.***: ***@***.***
6 info lifecycle ***@***.***: ***@***.***
7 verbose lifecycle ***@***.***: unsafe-perm in lifecycle true
8 verbose lifecycle ***@***.***: PATH:
/usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/odas_web/node_modules/.bin:/home/pi/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle ***@***.***: CWD: /home/pi/odas_web
10 silly lifecycle ***@***.***: Args: [ '-c', 'electron .' ]
11 silly lifecycle ***@***.***: Returned: code: 1 signal: null
12 info lifecycle ***@***.***: Failed to exec start script
13 verbose stack Error: ***@***.*** start: electron .
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.
(/usr/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.
(/usr/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:1022:16)
13 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:287:5)
14 verbose pkgid ***@***.***
15 verbose cwd /home/pi/odas_web
16 verbose Linux 5.15.76-v8+
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v12.22.12
19 verbose npm v6.14.16
20 error code ELIFECYCLE
21 error errno 1
22 error ***@***.*** start: electron .
22 error Exit status 1
23 error Failed at the ***@***.*** start script.
23 error This is probably not a problem with npm. There is likely
additional logging output above.
24 verbose exit [ 1, true ]
Running Debian Bullseye on pi4/8G
—
Reply to this email directly, view it on GitHub
<#83 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATHVRXQIFSNDJICQPNAUZJDWJ7PWBANCNFSM6AAAAAAQXPZBAI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
error. Cant npm start
error log
The text was updated successfully, but these errors were encountered: