[GH-ISSUE #12] "Node doesn't like ES6" (terminology) #9

New issue

Closed

opened 2026-05-05 11:23:00 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 11:23:00 -06:00

Owner

Originally created by @BillyWM on GitHub (Feb 17, 2018).
Original GitHub issue: https://github.com/kusti8/proton-native/issues/12

This is not true as of Node 6, where 99% of ES6 is supported with only 3 particular subfeatures missing (and Babel doesn't transpile them all for you, such as tail-call optimization).

Here's a chart: http://node.green

You may be thinking of other features that developers commonly use, like async/await or object rest/spread, but these are not part of "ES6" (ES2015) but rather later yearly standards revisions (ES2016 - ES 2018)

Many of these features are indeed supported in the most recent stable + LTS releases of Node (8 and 9) - the ones offered by default for download on the Node site

Originally created by @BillyWM on GitHub (Feb 17, 2018). Original GitHub issue: https://github.com/kusti8/proton-native/issues/12 This is not true as of Node 6, where 99% of ES6 is supported with only 3 particular subfeatures missing (and Babel doesn't transpile them all for you, such as tail-call optimization). Here's a chart: http://node.green You may be thinking of other features that developers commonly use, like async/await or object rest/spread, but these are not part of "ES6" (ES2015) but rather later yearly standards revisions (ES2016 - ES 2018) Many of these features are indeed supported in the most recent stable + LTS releases of Node (8 and 9) - the ones offered by default for download on the Node site

gitea-mirror closed this issue

2026-05-05 11:23:04 -06:00

gitea-mirror commented

2026-05-05 11:23:09 -06:00

Author

Owner

@kusti8 commented on GitHub (Feb 18, 2018):

Ok, I think I just had an old version of node on my computer, so that's why. I'll fix it now.

@kusti8 commented on GitHub (Feb 18, 2018): Ok, I think I just had an old version of node on my computer, so that's why. I'll fix it now.

gitea-mirror referenced this issue

2026-05-05 11:56:01 -06:00

[PR #15] [CLOSED] Use React event naming conventions #224