Strange problem solved: Cypress failed to start. This is usually caused by a missing library or dependency. (Cypress 3.1.0 on Windows 10)

See original GitHub issue

For several hours I struggled with the following problem when trying to run Cypress. After many tries, with all published tips and issues, I found out that the problem was related to the environment on my computer. Because my case could be very helpful to others, I post it here.

Concretely the problem was the setting: NODE_OPTIONS=–trace-warnings (that setting was related to a totally different case 2 years ago). When I … set NODE_OPTIONS= … all problems disappeared.

Cypress failed to start.
This is usually caused by a missing library or dependency.
The error below should indicate which dependency is missing.
https://on.cypress.io/required-dependencies
If you are using Docker, we provide containers with all required dependencies installed.
----------
Command failed: C:\Users\...\AppData\Local\Cypress\Cache\3.1.0\Cypress\Cypress.exe --smoke-test --ping=558

NVM: 1.1.5 NodeJS: 10.2.1 NPM: 5.6.0

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:7 (3 by maintainers)

Top GitHub Comments

2reactions

shlomiassafcommented, Mar 26, 2019

Can confirm that unset NODE_OPTIONS worked for me in Azure Devops using Hosted Ubuntu 1604.

Without it I got the same error.

1reaction

realtebocommented, Oct 22, 2019

I’ve the same issue but on Windows 10. Could it be the same cause? If yes, where/how to unset NODE_OPTIONS ?

I’m running Cypress using

yarn run cypress run

I get his

Cypress failed to start.

This is usually caused by a missing library or dependency.

The error below should indicate which dependency is missing.

https://on.cypress.io/required-dependencies

If you are using Docker, we provide containers with all required dependencies installed.

----------

Command failed: C:\Users\Utente\AppData\Local\Cypress\Cache\3.4.1\Cypress\Cypress.exe --smoke-test --ping=732

----------

Platform: win32 (10.0.18362)
Cypress Version: 3.4.1
error Command failed with exit code 1.

Same esit running verify

Top Results From Across the Web

Cypress failed to start on Windows - Stack Overflow

1 Cypress failed to start. This is usually caused by a missing library or dependency. The error below should indicate which dependency is...

cypress-io/cypress - Gitter

Cypress failed to start. This is usually caused by a missing library or dependency. The error below should indicate which dependency is missing....

cypress failed to start windows

(Version Cypress 3.1.0 on Windows 10) Strange problem solved: Cypress failed to start. This is usually caused by a missing library or dependency....

Troubleshooting | Cypress Documentation

If you're having an issue during installation of Cypress, try removing the contents of the Cypress cache. This will clear out all installed...

Debian -- Software Packages in "bullseye"

... armhf, i386, mips64el, mipsel, ppc64el, s390x]): advanced PC-speaker beeper - minimal package; beets (1.4.9-7): music tagger and library organizer ...