cypress: Cypress doesn't load or open its window
Current behavior
Cypress won’t load and it is indicating a vague cannot find module when I’ve upgraded to v10.1.0 it was working previously with 9.7.0 where it loads all spec lists. I did try the following:
cypress open -b chrome --e2ecypress open
all of the above did was open the window but it is stuck in a loading state.
Debug logs
node:internal/modules/cjs/loader:936
throw err;
^
Error: Cannot find module 'C:\Users\Jolambert'
Require stack:
- internal/preload
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at Module._preloadModules (node:internal/modules/cjs/loader:1276:12)
at loadPreloadModules (node:internal/bootstrap/pre_execution:483:5)
at prepareMainThreadExecution (node:internal/bootstrap/pre_execution:77:3)
at node:internal/main/run_main_module:7:1 {
code: 'MODULE_NOT_FOUND',
requireStack: [ 'internal/preload' ]
}
Cypress Version
10.1.0
Package Manager
yarn
Operating system
Windows
Other
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 4
- Comments: 32 (10 by maintainers)
This will be fixed in https://github.com/cypress-io/cypress/pull/22550 which we are going to review and release asap. Thanks for the patience everyone.
I have the same problem.
Can confirm the continuation of the path should be C:\Users\Samuel Preston.… I suspect the space hasn’t been handled properly.
10.2.0 is experiencing this issue. Downgraded to 10.0.3
By leaving my Windows machine logged in to the profile with the space in the name, I was able to reproduce this issue while testing the reproduction provided in another issue: https://github.com/cypress-io/cypress/issues/22303#issuecomment-1157538846
Here is the example that reproduces the issue: rename-files.zip
What seems to be in common between this project and some of the info provided above is typescript, so it’s possible some of the changes around typescript detection between 10.0.3 and 10.1.0 introduced this issue.