-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
First time ever npm install cypress
never finishes
#30779
Comments
@alexsch01 Is this specific to 13.17.0? Can you provide DEBUG logs? |
Nope |
I wasn't able to reproduce this on a fresh directory. We'd need some more information to debug this. |
Probably a npm issue since I don't see any debug information with |
npm 10.9.0 has this issue |
If the issue repeats itself, then refer to the troubleshooting steps on https://docs.cypress.io/app/references/advanced-installation#Troubleshoot-installation which list the following instructions to collect debug logs: CYPRESS_INSTALL_BINARY=0 npm install cypress --save-dev
DEBUG=cypress:cli* npx cypress install |
@MikeMcC399 yeah I believe it was a npm specific issue since none of the DEBUG logs were showing |
I was unable to reproduce your problem on Fedora 41 with your version of Node / npm. Without logs it won't be possible to diagnose. If it is all working now then there is no need to dig deeper. |
Removing $HOME/.npm folder and removing node_modules directory in project folder npm 10.9.1 doesn't for me |
Executing the following under Fedora 41, Node.js rm -rf ~/.npm
rm -rf ~/.cache/Cypress
rm -rf node_modules
CYPRESS_INSTALL_BINARY=0 npm install cypress --save-dev
DEBUG=cypress:cli* npx cypress install Logs
|
Current behavior
First time running the command
npm install cypress
, it never completesWhen I run it the second time, it will finish
Desired behavior
No response
Test code to reproduce
Doesn't apply to the issue
Cypress Version
13.17.0
Node version
v22.11.0
Operating System
Fresh Fedora 41 toolbox with nodejs
Debug Logs
No response
Other
Not a regression
The text was updated successfully, but these errors were encountered: