-
Notifications
You must be signed in to change notification settings - Fork 118
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
Error while running the nmp install & nmp start #2
Comments
To be precise I'm getting this error, i have the latest nodejs & npm and im getting this error.
|
Hey this seems to be issue with Electron itself for now you can use on other systems Windows, OSX and Linux installed on Windows |
@plutob0i Using npm install --unsafe-perm=true is ok |
Hello, I'm facing this error while iinstalling the tool,
sudo npm install
[sudo] password for kali:
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! electron@11.2.0 postinstall:
node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the electron@11.2.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-02-02T06_58_07_492Z-debug.log
kali@kali:
/XSSTRON$/XSSTRON$ sudo npm startkali@kali:
sh: 1: electron: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! XSSTRON@1.0.0 start:
electron .
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the XSSTRON@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-02-02T06_58_21_984Z-debug.log
The text was updated successfully, but these errors were encountered: