-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
chore: require Node 16.14 #7501
Conversation
Sigh I think we'll go to |
✅ [V2]
To edit notification comments on pull requests, go to your Netlify site settings. |
⚡️ Lighthouse report for the deploy preview of this PR
|
✅ [V2]
To edit notification comments on pull requests, go to your Netlify site settings. |
Size Change: 0 B Total Size: 796 kB ℹ️ View Unchanged
|
The error cause language feature was added in 16.10, but apparently we need 16.14 if we want proper nested stacktrace logging (separate node PR/feature) The minor version diff may not change much for users so what about moving directly to >= 16.14 + >= 18.0 ? This way we can safely finally use error-cause |
OK! This is a huge leap forward. |
👍 |
Pre-flight checklist
Motivation
Required for #7463.
@slorber
Error.prototype.cause
is added in v16.10, so if we want to use that, we have to go to 16.10.Test Plan
Test links
Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs