Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can we get a node-16 executor?

See original GitHub issue

There should be an executor to run on node 16. The max is 14 according to https://circleci.com/developer/orbs/orb/cypress-io/cypress#executors.

I haven’t ran into an issue yet but we’ve had some local issues with our postinstall scripts on node 14 so we’re bumping to 16 and I want to run the Cypress job on 16 too.

See https://nodejs.org/en/about/releases/; node 16, 17, and 18 should probably be supported.

Issue Analytics

State:
Created 2 years ago
Reactions:10
Comments:6 (1 by maintainers)

Top GitHub Comments

9reactions

FinnLawrencecommented, Mar 6, 2022

For anyone who needs Node 16 support in the meantime, I have set our builds up to use a customised docker executor from Cypress’s list here: https://github.com/cypress-io/cypress-docker-images/tree/master/browsers

Example config:

version: 2.1
orbs:
  cypress: cypress-io/cypress@1.29.0
executors:
  with-chrome:
    resource_class: small
    docker:
      - image: "cypress/browsers:node16.13.0-chrome95-ff94"
workflows:
  build:
    jobs:
      - cypress/install:
          executor: with-chrome
          ....
      - [your other jobs]
          executor: with-chrome
          ....

0reactions

adam-lynchcommented, Jul 21, 2022

Thanks a lot @admah!

My tests run fine. I now see the “CertVerifyProcBuiltin” error (https://github.com/cypress-io/cypress/discussions/22128). I assume this is unrelated to the executor and I’ve only starting seeing it because my Circle cache was cleared due to changing the Node version.