You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it's bad practice for Cypress (or any other package) to be injecting GitHub URLs into package lockfiles, for exactly this reason. In my experience, the npm CDN is much more reliable. Also, we use an internal npm registry - which I'm sure many other organizations do as well - which caches package downloads, but that cache doesn't work if Cypress is trying to download directly from GitHub.
Whatever is being downloaded should be package-ified and put on npm, just like everything else. Or, it should be included in the Cypress binary. We're also caching that locally, but this GitHub URL circumvents that cache as well.
Versions
Cypress: 4.1.0
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Current behavior:
A GitHub URL is put into the lockfile, which is much less reliable than an npm package.
Desired behavior:
Only npm packages should be downloaded.
Details
Last night, our builds failed for the better part of 4 hours because
yarn install
failed with this error:I think it's bad practice for Cypress (or any other package) to be injecting GitHub URLs into package lockfiles, for exactly this reason. In my experience, the npm CDN is much more reliable. Also, we use an internal npm registry - which I'm sure many other organizations do as well - which caches package downloads, but that cache doesn't work if Cypress is trying to download directly from GitHub.
Whatever is being downloaded should be package-ified and put on npm, just like everything else. Or, it should be included in the Cypress binary. We're also caching that locally, but this GitHub URL circumvents that cache as well.
Versions
Cypress: 4.1.0
The text was updated successfully, but these errors were encountered: