-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Your configFile is invalid with Node.js 22.12.0 #30715
Comments
@fredrik-jansson-se What version was this previously working find on? |
@jennifer-shehane, this was working on 13.15.0. Thanks for getting back to me! |
Please let me know if I can gather any other info. |
I've a put a minimal (I hope) reproducing example there. |
Changing on('after:spec', (_spec: Cypress.Spec, results: CypressCommandLine.RunResult) => to seems to fix it. on('after:spec', (_spec, results) => { I get this error before the change.
Not sure what to make of this... |
EDIT: This didn't work in the end. I'm not sure why it seemed to have work, but I might have changed multiple things at once without noticing
This worked for me too. Thanks ! Very weird though. In my case I went from function setupNodeEvents(on: Cypress.PluginEvents, config: Cypress.PluginConfigOptions) to function setupNodeEvents(on, config) |
@FelixNumworks, so you have similar issues in your project or did you (kindly) test my stuff? :) |
@fredrik-jansson-se I have similar issue. It seems to arise after updating Node to v22. I'm not sure yet, I need to investigate |
@FelixNumworks , thanks! I had the issue on Node v20, upgrading to Node v22 didn't make it worse. |
@FelixNumworks, it might help you with your search: it worked in 22.11.0 and now fails in 22.12.0 and @jennifer-shehane I wouldn't be surprised if it has to do with https://nodejs.org/en/blog/release/v22.12.0#requireesm-is-now-enabled-by-default |
This issue started happening in our pipelines that used the |
Using NODE_OPTIONS="--no-experimental-require-module" cypress ... when running Cypress fixed the problem entirely for me. Thank you @jraoult for pointing the right Node docs
|
We're taking a look at this. |
Hi @mschile , do you know when this will release? |
@awsluja, it's scheduled to be released tomorrow. In the meantime, you can use this workaround. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
Desired behavior
Cypress should run
Test code to reproduce
Cypress Version
13.16.0
Node version
v20.12.2
Operating System
macOS 15.1.1
Debug Logs
Other
No response
The text was updated successfully, but these errors were encountered: