Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cypress no longer works on AWS CodeBuild
See original GitHub issueCypress 2.x no longer works on AWS CodeBuild. I get this error during the testing phase:
error cypress@2.0.3: The engine "node" is incompatible with this module. Expected version ">=8.2.1".
What’s the recommended course of action here?
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
AWS CodeBuild - Cypress Documentation
With AWS CodeBuild Amazon Web Services (AWS) offers developers "...a fully managed build service that compiles your source code, runs unit tests, ...
Read more >Running Cypress Tests on AWS CodeBuild - Chariot Solutions
Cypress is a relatively new web testing tool that is easier to use than Selenium, and it's gaining in popularity.
Read more >Integrating Cypress E2E tests with AWS CodeBuild CI/CD
A few weeks ago we set up CI/CD with AWS CodeBuild on our team. It hasn't really changed our workflow, but there are...
Read more >Cypress cy.wait doesn't work on AWS CodeBuild
I checked my server logs and I see the API request received, so the problem is Cypress that doesn't understand if the API...
Read more >Running Cypress end-to-end tests in parallel using AWS ...
Implementing an AWS Codepipeline for running end-to-end tests with AWS ... is tolerable (no more than 15 minutes), but the money is not....
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
We’ll get a patch release out this weekend.
Seems we are overwriting engines in the CLI package.json with engines from the root package. This is wrong. When testing we should set config value to error in this case (https://docs.npmjs.com/misc/config#engine-strict) and then fix the engines property.