question-mark
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 9.1.1 + Node 17.2 (Win 11) Crashes

See original GitHub issue

Current behavior

Same as issue which is fixed for Cypress v9.1.1. and Node 17.1 seems to have returned for Cypressv9.1.1. and Node 17.2 : https://github.com/cypress-io/cypress/issues/18914

Desired behavior

No response

Test code to reproduce

no test code required

Cypress Version

9.1.1.

Other

Adding "nodeVersion": "bundled" in the cypress.json works around the issue.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:14
  • Comments:17 (8 by maintainers)

github_iconTop GitHub Comments

9reactions
ivandjorgoncommented, Dec 14, 2021

I am experiencing the same issue on MacOS (11.2.1, Big Sur). I upgraded from cypress 9.1.0 to version 9.1.1 and this immediately started happening; no issues whatsoever beforehand while on version 9.1.0.

I’ve been on node version 17.0.1 & npm version 8.1.0 for a while.

Steps to reproduce: Upgrade cypress from 9.1.0 to 9.1.1 via command npm install --save-dev cypress@9.1.1

–> Unable to launch cypress test runner or run in headless mode –> Received the following message output in the terminal …/17.0.1/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

Workaround: As was mentioned, adding “nodeVersion”: “bundled” in the cypress.json temporarily fixes the issue

3reactions
rdar-labcommented, Dec 19, 2021

The workaround works, but, you get this message:

Deprecation Warning: nodeVersion is currently set to bundled in the cypress.json configuration file. As of Cypress version 9.0.0 the default behavior of nodeVersion has changed to always use the version of Node used to start cypress via the cli. When nodeVersion is set to bundled, Cypress will use the version of Node bundled with electron. This can cause problems running certain plugins or integrations. As the nodeVersion configuration option will be removed in a future release, it is recommended to remove the nodeVersion configuration option from cypress.json.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Changelog - Cypress Documentation
When a chromium based browser tab or process crashes, Cypress will no longer hang indefinitely but will fail the current test and move...
Read more >
npm WARN npm npm does not support Node.js v9.1.0
It turns out that the current installed npm is not compatible with the new node and has a hard time updating. The solution...
Read more >
How To Fix Cypress Crashing Issue In Windows - YouTube
In this video, we will discuss how to fix the cypress crashing issue.New Selenium Batch Starting ...
Read more >
cypress: Versions - Openbase
Changelog: https://docs.cypress.io/guides/references/changelog#11-2-0 ... This prevents Cypress from crashing when a user has Node 17 installed which was ...
Read more >
cypress - npm
What is this? Cypress comes packaged as an npm module, which is all you need to get started testing. After installing you'll be...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found