TL enforces cypress 4.0.1
See original GitHub issuecypress-testing-library
version: 5.3.0node
version: 2.14.0npm
(oryarn
) version: yarn 1.21.1
Relevant code or config package.json
{
"name": "cypress-example-docker-gitlab",
"version": "1.0.0",
"description": "> Cypress + Docker + GitLabCI = ❤️",
"main": "index.js",
"private": true,
"scripts": {
"test": "cypress run"
},
"repository": {
"type": "git",
"url": "git+ssh://git@gitlab.com/cypress-io/cypress-example-docker-gitlab.git"
},
"keywords": [
"cypress",
"cypress-io",
"example",
"gitlab"
],
"author": "gleb@cypress.io",
"license": "ISC",
"bugs": {
"url": "https://gitlab.com/cypress-io/cypress-example-docker-gitlab/issues"
},
"homepage": "https://gitlab.com/cypress-io/cypress-example-docker-gitlab#README",
"devDependencies": {
"cypress": "3.8.3",
"@testing-library/cypress": "^5.3.0"
}
}
What you did:
I cloned the cypress gitlab example and added the testing library cypress dependency (as seen in the package.json above) and bumped the cypress version to 3.8.3. I then run cypress in a docker container:
docker run --rm -it -v /<path to repo>/:/<new dir>/ cypress/browsers:node12.14.0-chrome79-ff71 bash
What happened:
While doing yarn
inside the container I receive an error! Apparently, yarn tries to install two versions of Cypress (3.8.3 and 4.0.1). I remove the TL dependency the error disappears. Not sure whether this expected behaviour or whether the provided peerDependency in TL should handle this?
The Cypress App could not be downloaded.
Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration
Otherwise, please check network connectivity and try again:
----------
URL: https://download.cypress.io/desktop/4.0.1?platform=linux&arch=x64
Error: Corrupted download
Expected downloaded file to have checksum: 7e26904b56c560f9ba893085903b8435c651a86058b4ba81075f51158e4846e884a039c473d07ce74ef93ab8134164e8fe6eac192a8fababe99fc13ce757310e
Computed checksum: 12c7e488d3ff1f7452979b64972d7ed3b12ca127f2f388abdf816660509fa37034aae50256d91da0affb9eeefaad4fd01eff07e60839e15513516c4af02f869a
Expected downloaded file to have size: 167819701
Computed size: 167819701
----------
Platform: linux (Debian - 9.11)
Cypress Version: 4.0.1
The Cypress App could not be downloaded.
Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration
Reproduction repository:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:31 (13 by maintainers)
Top Results From Across the Web
Changelog - Cypress Documentation
In Cypress 12, we enforce running tests in a clean browser context through test isolation. This option is configurable, but is enabled by...
Read more >CMS quality reporting programs Testing And Certification Tool
Enforces reporting requirements defined by the CMS QRDA Implementation Guides. ... The Cypress 4.0.1 patch was released on 10/11/18.
Read more >Changelog — elabftw 4.4.2 documentation
Fix update issue with databases enforcing primary keys (e.g. DO cluster). Allow admin to unlock entry, and allow unlock ... Use cypress for...
Read more >Changelog - sorry-cypress
Sorry Cypress changelog. ... Deprecated support for cypress agents lt 6.7.0. Supporting the legacy versions of cypress with all the code was cumbersome....
Read more >cypress-testing-library - bytemeta
TL enforces cypress 4.0.1 · support for cypress v4 · Revert changes to query*s and add deprecation warning.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Type Defs are now built-in, so this shouldn’t be a problem anymore.
I understand your position and I’ve suggested a solution. I don’t have the bandwidth to work on it right now, but I’d welcome anyone to make a PR to internalize the types or even rewrite to TypeScript if they want to. I think that removing the dependency would be a breaking change and I’m not prepared to do that at the moment.