-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Overriding Node version with cypress.config.ts has no effect #29539
Comments
We removed the |
@jennifer-shehane I did see that but assumed Can you share the correct way to specify a node path/version, if I'm not using the correct configs? |
What are you trying to accomplish exactly? |
You need to install the version of Node.js that you want to use. Since you are on Windows you may consider installing and using a Node.js manager, such as nvm-windows https://github.com/coreybutler/nvm-windows/releases/tag/1.1.11, which allows you to switch between Node.js versions. |
What I was hoping to do was use the node executable that is bundled with my application repo (legacy architecture/paradigms) rather than the node version installed on my ci runners. |
What CI system are you using? GitHub Actions or something else? This is more of a "how-to" question which typically gets discussed in Discord, but we can continue here for your next steps. |
Current behavior
I couldn't find documentation on how to use the node version configs, so I'm wondering if I'm missing some other element or if this is a defect. The node version & path in config have no effect:
My test output still references version 18:
Thanks!
Desired behavior
use specified node version instead of the bundled version
Test code to reproduce
Cypress Version
13.9.0
Node version
20.9.0
Operating System
Windows
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: