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
Installing etheratom errors #152
Comments
try install https://github.com/felixrieseberg/windows-build-tools |
Worked, thanks! |
@fanatid's Your solution does work, thanks! What do you think the root problem is, @barrysteyn? Many people seem to be facing the same issue when installing some modules on Windows 7, e.g. |
|
I am getting warning on ubuntu: npm WARN lifecycle scrypt@6.0.3~preinstall: cannot run in wd %s %s (wd=%s) scrypt@6.0.3 node node-scrypt-preinstall.js /usr/lib/node_modules/.staging/scrypt-337cb8ab |
Hey, When I try to install etheratom, it fails with this error:
npm ERR! node v6.9.5
npm ERR! npm v3.10.5
npm ERR! code ELIFECYCLE
npm ERR! scrypt@6.0.3 install:
node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the scrypt@6.0.3 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the scrypt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs scrypt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls scrypt
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! %AppData%\Local\Temp\apm-install-dir-117424-6572-1ax57bw.037rwfjemi\npm-debug.log
npm ERR! code 1
I am running Win10 & have the latest node.js. Now, the file it tells me to provide (in the end) doesn't exist, but I found another log in the Atom_crashes ffolder with a current timestamp that might help ...
operation_log.txt
The text was updated successfully, but these errors were encountered: