You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node 8 has reached end-of-life as of December 31, 2019 (link). Is there a formal timeline for when TypeScript will drop support for the platform?
Use Cases
#35957 has build errors in Node 8 for capture groups not being supported (though, admittedly, I am dubious about relying on the platform's RegExp constructor in the compiler...).
Checklist
My suggestion meets these guidelines:
[❌?] This wouldn't be a breaking change in existing TypeScript/JavaScript code
This wouldn't change the runtime behavior of existing JavaScript code
This could be implemented without emitting different JS based on the types of the expressions
This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
While we'll likely stop having CI for node 8 soon (and instead have 13, 12, 10), I don't think we'll intentionally land features that rely on es6+ runtime behaviors (without also providing a polyfill) if we can help it.
Search Terms
node 8 10 eol end of life deprecation
Suggestion
Node 8 has reached end-of-life as of December 31, 2019 (link). Is there a formal timeline for when TypeScript will drop support for the platform?
Use Cases
#35957 has build errors in Node 8 for capture groups not being supported (though, admittedly, I am dubious about relying on the platform's
RegExp
constructor in the compiler...).Checklist
My suggestion meets these guidelines:
The text was updated successfully, but these errors were encountered: