-
Notifications
You must be signed in to change notification settings - Fork 232
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
V4 update node requirements #591
Comments
Should support Node 14-18 |
Node 18 should support native |
node 14 support ends this April, I suggest we drop node 14 support. Node 16 EOL is this September, dropping that would be "harsh" but it'd solve a lot of polyfills issues :) |
I don't know if a library like ours should trigger Node updates to folks upstream. What are we losing with dropping 14? |
My expectation is that most cloud providers are going to match node's support policy see azure and aws hasn't announced v14 EOL yet, but 12 EOL matched nodejs support policy + 1 year |
Updates to this issue. V4 will support Node 18-20. This is already done. |
No description provided.
The text was updated successfully, but these errors were encountered: