file name contains character ”+“ not run

[mingyixu]

the file cy_web+_20191207220608.js is exsite, but run cypress,

Cannot find module web _20191207220608.js, this character ”+“  instead of " ", so not find the file.

Current behavior:

  │ Cypress:    3.7.0                                                                              │
  │ Browser:    Electron 73 (headless)                                                             │
  │ Specs:      1 found (web+_20191207220608/web+_20191207220608.js)                    │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘


────────────────────────────────────────────────────────────────────────────────────────────────────
                                                                                                    
  Running:  web+_20191207220608/web+_20191207220608.js                           (1 of 1)

Oops...we found an error preparing this test file:

  /home/admin/cypress/web _20191207220608/web _20191207220608.js

The error was:

Error: Cannot find module '/home/admin/cypress/web _20191207220608/web _20191207220608.js' from '/home/admin/cypress'

This occurred while Cypress was compiling and bundling your test code. This is usually caused by:

- A missing file or dependency
- A syntax error in the file or one of its dependencies

Fix the error in your code and re-run your tests.

[jennifer-shehane]

Yes, confirmed. Specfiles with + character do not run in Cypress.

The error seems to print the filename with the + character replaced with a character.

My file was at cypress/integration/foo+bar.js

[emchoi7]

Could I take a look at this, if nobody else is already?

[jennifer-shehane]

@emchoi7 Sure

[jennifer-shehane]

Reopening as this is still an issue.

[jennifer-shehane]

The code for this is done in cypress-io/cypress#8015, but has yet to be released.

We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 4.12.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v4.12.0, please open a new issue.