Skip to content

Is Node 8 still supported? #35958

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

Closed
4 tasks done
JoshuaKGoldberg opened this issue Jan 2, 2020 · 2 comments
Closed
4 tasks done

Is Node 8 still supported? #35958

JoshuaKGoldberg opened this issue Jan 2, 2020 · 2 comments

Comments

@JoshuaKGoldberg
Copy link
Contributor

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:

  • [❌?] 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.)
  • This feature would agree with the rest of TypeScript's Design Goals.
@weswigham
Copy link
Member

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.

@JoshuaKGoldberg
Copy link
Contributor Author

Thanks!

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

No branches or pull requests

2 participants