Skip to content
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

remove support for Node.js 14 and 16 #2325

Closed
davidjgoss opened this issue Sep 6, 2023 · 0 comments · Fixed by #2331
Closed

remove support for Node.js 14 and 16 #2325

davidjgoss opened this issue Sep 6, 2023 · 0 comments · Fixed by #2331
Assignees
Labels
🏦 debt Tech debt 💔 breaking change This will require a major release
Milestone

Comments

@davidjgoss
Copy link
Contributor

davidjgoss commented Sep 6, 2023

Currently we support Node.js 14 and 16. Per their release schedule, 14 has already been EOL'd, and 16 will follow on 11 Sep 2023 - in just a few days time as I write this.

For our next major release (10.0.0), we should drop both 14 and 16.

Once this is done, we'll be able to explore adopting some newer features, including node: import specifiers and even WHATWG streams. We could also reduce some dependencies by using new JavaScript and Node.js utils like structuredClone and tmpdir.

Also, we can go upstream and apply this to the various @cucumber/* libraries like gherkin etc.

(A note for future, we ought to be more prompt about following suit when Node.js EOL's a release, as it always brings benefits and helps move the ecosystem along.)

@davidjgoss davidjgoss added 💔 breaking change This will require a major release 🏦 debt Tech debt labels Sep 6, 2023
@davidjgoss davidjgoss added this to the 10.0.0 milestone Sep 6, 2023
@davidjgoss davidjgoss self-assigned this Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏦 debt Tech debt 💔 breaking change This will require a major release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant