npm ci: executable not accessible from cypress
See original GitHub issueversion: 2.1
orbs:
# import Cypress orb by specifying an exact version
cypress: cypress-io/cypress@1.5.0
workflows:
version: 2.1
build_and_deploy_staging:
jobs:
- build
- deploy-staging:
requires:
- build
filters:
branches:
only: master
- cypress/run:
record: true
parallel: false
requires:
- deploy-staging
filters:
branches:
only: master
This is weird, the CI has stopped working using the yml in circleCI. Do i need to change where to store the cache?
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Cypress failed to start on Windows - Stack Overflow
Tried opening Cypress using the prompt: node_modules.bin\cypress open but got the below message but there was no error listed. Has anyone come across...
Read more >Installing - Cypress Documentation
npm install This will install Cypress locally as a dev dependency for your project. Make sure that you have already run npm init...
Read more >Installing Cypress - w3resource
If you installed Cypress using npm, Cypress is installed to your ./node_modules directory, and the binary executable is accessible from .
Read more >@cypress/github-action - npm
If you re-run the GitHub workflow, if you use the same custom build id during recording, Cypress Cloud will cancel the run with...
Read more >What are the differences between npm and npx - GeeksforGeeks
If you have installed npm below 5.2.0 then npx is not installed in your ... A package can be executable without installing the...
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 FreeTop 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
Top GitHub Comments
Wow that is an interesting error, thanks for tracking it down
Sent from my iPhone
That is the error! Ok finally figure it out! It is because of package-lock.json issue. My teammate had some older version of package-lock.json pushed without updating the lock file. That lock file didn’t have cypress within it. When running
npm ci
, it was throwing errors.