Skip to content
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 the latest 1.54.0 package on Windows fails #777

Closed
georgiosd opened this issue Jun 28, 2020 · 7 comments
Closed

Installing the latest 1.54.0 package on Windows fails #777

georgiosd opened this issue Jun 28, 2020 · 7 comments

Comments

@georgiosd
Copy link

From admin powershell prompt:

C:\Windows\system32> npm install -g @sentry/cli
C:\Users\georgiosd\AppData\Roaming\npm\sentry-cli -> C:\Users\georgiosd\AppData\Roaming\npm\node_modules\@sentry\cli\bin\sentry-cli

> @sentry/cli@1.54.0 install C:\Users\georgiosd\AppData\Roaming\npm\node_modules\@sentry\cli
> node scripts/install.js

Error: Command failed: C:\Users\georgiosd\AppData\Roaming\npm\node_modules\@sentry\cli\sentry-cli.exe --version

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @sentry/cli@1.54.0 install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @sentry/cli@1.54.0 install 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!     C:\Users\georgiosd\AppData\Roaming\npm-cache\_logs\2020-06-28T18_38_17_562Z-debug.log
@alex-adestech
Copy link

@georgiosd this solved the issue for me. #744 (comment)

@georgiosd
Copy link
Author

@alex-adestech thanks, but I am already working with 12.x

@kamilogorek
Copy link
Contributor

Can you provide a log mentioned in the original post? Or is it the same thing you already pasted?

@georgiosd
Copy link
Author

@kamilogorek log above is with node 12.x, yes. Is that what you meant?

@kamilogorek
Copy link
Contributor

I was wondering if C:\Users\georgiosd\AppData\Roaming\npm-cache\_logs\2020-06-28T18_38_17_562Z-debug.log contains anything more than what you already provided.

@kamilogorek
Copy link
Contributor

kamilogorek commented Jul 1, 2020

It's hard to tell what went wrong, as node doesn't give enough context for the failure.
I'd start with the lowest hanging fruits first:

npm cache clean --force, delete C:\Users\georgiosd\AppData\Roaming\npm\node_modules (or more specific @sentry directory) and then try to create the directory yourself and give it executable permissions. Sometimes doing just that fixes npm issues.

Also, see https://stackoverflow.com/questions/42308879/npm-err-code-elifecycle for some more ideas

@georgiosd
Copy link
Author

Not sure but it's not happening any more. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants