Rework CYPRESS_RUN_BINARY instructions #6024
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Advanced Installation > Run binary includes instructions for using the environment variable
CYPRESS_RUN_BINARY
to override where the npm module finds the Cypress binary.npx
,yarn
orpnpm
is missing and there is no hint that this would be needed.cypress.zip
. Depending on how the extract or unzip operation is performed, there may be an extra directory level created. On Linux, for instance, this could mean that it is necessary to set the environment variable toCYPRESS_RUN_BINARY=~/Downloads/cypress/Cypress/Cypress
instead ofCYPRESS_RUN_BINARY=~/Downloads/Cypress/Cypress
. This is quite confusing considering the multiple use of the namescypress
andCypress
as directories andCypress
as an executable.binary_state.json
is read-only cypress#30684). There is no mention of this issue or a possible workaround.CYPRESS_RUN_BINARY
environment variable, does not make a lot of sense.Change
The instructions in Advanced Installation > Run binary for using the environment variable
CYPRESS_RUN_BINARY
are reworked.