r/node • • Apr 23 '19

Introducing Node.js 12

https://medium.com/@nodejs/introducing-node-js-12-76c41a1b3f3f
44 Upvotes

15 comments sorted by

11

u/EntroperZero Apr 23 '19

Sigh. AWS Lambda is still on Node 8. They just recently rolled out Node 10 in Elastic Beanstalk.

3

u/jadbox Apr 24 '19

My thoughts exactly, although you can use your own 'stacks' now, but afaik, they still increase execution time for first runs.

11

u/PM_ME_DON_CHEADLE Apr 24 '19

omfg import statements fucking finally.

1

u/[deleted] Apr 24 '19

[removed] — view removed comment

2

u/Lukalinda Apr 24 '19

No not yet. They hope for it to be by October when node 12 enters LTS.

1

u/[deleted] Apr 24 '19

[removed] — view removed comment

1

u/Lukalinda Apr 24 '19

According to the article, yes. Read it. It's a good article.

4

u/NoInkling Apr 24 '19

List of some of the new ES features/APIs now available thanks to V8 7.4 (compared to 7.0 in Node 11):

  • Class fields (both public and private)

  • Object.fromEntries

  • String.prototype.matchAll

  • Some new Intl APIs

6

u/ATHP Apr 23 '19

I like the private fields. Good move in the right direction.

5

u/Capaj Apr 23 '19

I hate them. Gone are the days when you could simply monkey patch anything you might encounter at runtime.

4

u/SnowyMovies Apr 24 '19

Should be able to be solved by reflection.

3

u/ecares Apr 24 '19

Actually no, they decided to prevent that and I'm pretty mad too

1

u/[deleted] Apr 24 '19

Can't wait to try out async stack traces. At the moment async/await can quickly turn into a debugging nightmare.

1

u/a-corsican-pimp Apr 25 '19

I can't seem to find the answer: are they still hidden behind a flag?