-
Notifications
You must be signed in to change notification settings - Fork 455
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
drop Node.js v16 (EoL) support #6429
Conversation
I understand there are concerns about drastically increasing the supported Node.js version How about dropping Node.js v15 or lower? We already do testing only on v16. (v16.x has complete ESM support, including support for top-level await) Gradual Node.js version upgrades will help us maintain a thin JS wrapper as Node.js itself is becoming useful. |
@cristianoc @zth How shall we proceed with this? |
fyi what are new features in nodejs, useful for rescript peers and compiler itself.
|
@cometkim Could you rebase and move the changelog entry to 12.0.0-alpha.1? |
@cknitt done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
A lot of follow-up work is possible to modernize our dev env and js wrapper |
* drop Node.js v16 (EoL) support * add CHANGELOG
The official maintenance for Node 16 ended last October. Perfect timing
This won't break anything right away, but it should be marked as a breaking change. Then we can make further improvements in the JS part in the future