cypress: The Cypress App could not be downloaded (Can't install via NPM I on WINDOWS 2012)
Current behavior:
Can’t install any Cypress version.
I do not use a proxy, I can also download the required version via the browser and console.
STR: When I make:
npm install cypress --save-dev
I get:
URL: https://download.cypress.io/desktop/3.7.0?platform=win32&arch=x64
Error: read ECONNRESET
Desired behavior:
The installation of the module should be successful.
Test code to reproduce
Log:
> cypress@3.7.0 postinstall C:\projects\xxx\develop\node_modules\cypress
> node index.js --exec install
Installing Cypress (version: 3.7.0)
[09:45:47] Downloading Cypress [started]
[09:45:48] Downloading Cypress [failed]
[09:45:48] → The Cypress App could not be downloaded.
Does your workplace require a proxy to be used to access the Internet? If so, y ou must configure the HTTP_PROXY environment variable before downloading Cypres s. Read more: https://on.cypress.io/proxy-configuration
Otherwise, please check network connectivity and try again:
----------
URL: https://download.cypress.io/desktop/3.7.0?platform=win32&arch=x64
Error: read ECONNRESET
----------
Platform: win32 (6.3.9600)
Cypress Version: 3.7.0
The Cypress App could not be downloaded.
Does your workplace require a proxy to be used to access the Internet? If so, y ou must configure the HTTP_PROXY environment variable before downloading Cypres s. Read more: https://on.cypress.io/proxy-configuration
Otherwise, please check network connectivity and try again:
----------
URL: https://download.cypress.io/desktop/3.7.0?platform=win32&arch=x64
Error: read ECONNRESET
----------
Platform: win32 (6.3.9600)
Cypress Version: 3.7.0
npm WARN rollback Rolling back node-pre-gyp@0.14.0 failed (this is probably har mless): EPERM: operation not permitted, scandir 'C:\projects\xxx\develop\nod e_modules\fsevents\node_modules'
npm WARN eslint-config-airbnb@17.1.0 requires a peer of eslint@^4.19.1 || ^5.3. 0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-loader@2.1.2 requires a peer of eslint@>=1.6.0 <6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-airbnb-base@13.2.0 requires a peer of eslint@^4.19.1 || ^5.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\f sevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents @1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x6 4"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! cypress@3.7.0 postinstall: `node index.js --exec install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the cypress@3.7.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional lo gging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2020-02-04T 07_45_59_543Z-debug.log
Versions
Cypress 3.7.0
Operating System: Windows Server 2012 R2 Standard 64-bit (6.3, Build 9600) (9600.winblue_ltsb_escrow.191014-1700)
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 11
- Comments: 25 (4 by maintainers)
I always come back to this issue and find that it’s always the fact there are two instances in the lockfile. I fix it by forcing the correct version via the “resolutions” field in
package.json.This can be solved using
yarn upgrade cypressThis issue should be closed.
PS: I’m on a Mac OS
Getting this again today for 4.6.0. It seems like binaries get corrupted on some sort of random, self-resolving basis.
I got the same error on the azure pipeline but with yarn and I was able to workaround. log:
workaround
I remove from my package.json
@testing-library/cypress. I refactored my tests. I delete the node_modules folderrm -rf node_modulesI runyarn installand It works!!!I have the same “corruption” issue where the checksum fails, but the filesize matches. https://github.com/cypress-io/cypress/issues/7761
For no reason at all, after trying to go back to 3.8.3, and then re-downloading 4.8.0, it worked. amazing. Lost about 8+ hours to this.