-
Notifications
You must be signed in to change notification settings - Fork 101
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
Need help overriding node version 18.16.1 #467
Comments
@delusioninabox Could you share some of the output that shows Node 18.16.1 being used? |
@jennifer-shehane Of course! The
At the start of the
|
A working example on https://github.com/cypress-io/cypress-realworld-app/blob/develop/.circleci/config.yml is using version: 2.1
orbs:
cypress: cypress-io/cypress@3.3.1
codecov: codecov/codecov@1.2.3 #
executors:
with-chrome-and-firefox:
docker:
- image: "cypress/browsers:node-20.12.0-chrome-123.0.6312.86-1-ff-124.0.2-edge-123.0.2420.65-1"
resource_class: large
environment:
CYPRESS_coverage: false |
Yes, I initially tried with
|
|
@MikeMcC399 Yeah that works, although it would be nice to have the option for |
Agreed! I added some comment into #468 (comment) about this. |
Thanks y'all! Agreed that an option for |
|
|
Cypress is installing all my NPM packages by default with node version 18.16.1. Because of the older version, some of our packages appear to be installing older versions despite being newer versions in our package-lock file. We have a few tests that are flaky in circleci but run reliably locally, and I think they might be related, so I want our Cypress tests in circleci to run on a newer version to see if that resolves some of that inconsistency.
I have tried following the steps in the documentation and alternative configurations, but it runs on 18.16.1 every time regardless. Our setup is also set to work with circleci's "rerun failed tests" and following that documentation, if that matters. I tried different cypress/browsers for the image and had the same result.
Can someone help spot what I'm missing to get this running on a different node version than the default?
The text was updated successfully, but these errors were encountered: