Skip to content

Conversation

Rishi556
Copy link

No description provided.

@stianjensen
Copy link
Contributor

Nice! From April 30th 2025, 20 and 22 will be the only supported node versions:
https://endoflife.date/nodejs

Perhaps it makes sense to also drop support for node 14 and 16 soon.

@Rishi556
Copy link
Author

@stianjensen I’ll let the maintainers decide that. But as long as it works on a older version, I don’t see a need to drop it from the test matrix, can always remove it down the line when a breaking change is needed.

@YasharF
Copy link

YasharF commented Feb 1, 2025

I believe the question of running tests on older Node.js versions hinges on whether the package aims to support those versions. If tests start failing on older versions, should the code be modified to accommodate them? If no actions will be taken when compatibility with EOL (End of Life) versions of Node.js breaks, why would we continue running those tests? It's like adding unnecessary resource consumption without benefit. 🌎🔥

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants