Open krista-prokop opened 1 month ago
We removed the nodeVersion
config in v13: https://docs.cypress.io/guides/references/changelog#13-0-0
@jennifer-shehane I did see that but assumed nodeVersion
was different from the configs I'm using - resolvedNodeVersion
and resolvedNodePath
. Are you saying those 2 configs are deprecated too? I saw them still being referenced in the repo :/
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?
@krista-prokop
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.
@krista-prokop
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