package.json `engines` lists Node.js 14 in end-of-life status about cypress-example-kitchensink HOT 5 CLOSED

The main Cypress repo cypress-io/cypress uses Yarn and in the default develop branch it specifies:

  "engines": {
    "node": ">=16.16.0",
    "yarn": ">=1.17.3"
  },

so updating this repo should not cause a problem for building Cypress.

cypress-io/cypress/blob/develop/cli/package.json however specifies:

  "engines": {
    "node": "^14.0.0 || ^16.0.0 || >=18.0.0"
  },

which affects the released npm package cypress so I suggest delaying changes in the cypress-io/cypress-example-kitchensink until the engines definition of Cypress has been updated to a minimum Node.js 16 version.

from cypress-example-kitchensink.

@nagash77

Are there any plans to update engines for the Cypress 13.x release to drop Node.js 14 and explicitly add Node.js 20 (implicitly dropping Node.js 19)?

I can't see any change so far to engines in
https://github.com/cypress-io/cypress/blob/release/13.0.0/cli/package.json

https://github.com/cypress-io/cypress/blob/fb68512bfaa7d64a7308e16f5df1e88e49119ec3/cli/package.json#L125-L127 shows

  "engines": {
    "node": "^14.0.0 || ^16.0.0 || >=18.0.0"
  },

from cypress-example-kitchensink.

• Issue #721 should be resolved before making any changes to the engines definition.

• On Sep 11, 2023 Node.js 18 will become the earliest supported version according to the Node.js release schedule, so at some time after this date both ^14.0.0 and ^16.0.0 should be removed from the engines definition. Also the lockfileVersion could be updated to 3.

from cypress-example-kitchensink.

• cypress-io/cypress#27642 updates Cypress for the Cypress 13.x release, however
• #721 still needs to be resolved here first before updating engines in this repo

from cypress-example-kitchensink.

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from cypress-example-kitchensink.