node

He did say to "try" it, you can use a flag. You should assume that any feature behind a flag should never be used in production. Also, Node v7 will likely get a semver-minor update with V8 55. So, simply waiting for v7.3 or v7.4 should be sufficient and it will be enabled by default. https://github.com/nodejs/node/pull/9618#issuecomment-264641... Those who are sticking with the LTS release for production will need to wait until April/May 2017. March is overly optimistic by the OP as the currently scheduled date is 2017-04-30. https://github.com/nodejs/LTS

I don't know why there are so many non-answers or flat out incorrect answers to your question. Yes, js devs use debuggers and have for years. Firebug was created and popularized for browser js 10 years ago[1]. Node.js was released 7 years ago, got a debug option one year later using node debugger. It was CLI based and a bit shit. Tools which leveraged Node's debug protocol and Chrome's developer tools (node-inspector) for example were started 5 years ago[2]. Most recently some group associated (maybe on?) the Chrome team started creating a cleaner debug protocol and integrating directly with the Chromium project[3]. That's become the gold standard and is the standard way of debugging for Node 7+[4]. VSCode uses that protocol to offer debugging directly from the editor. 1. https://en.wikipedia.org/wiki/Firebug_(software) 2. https://github.

> Isn't that what we want, though? Generally. But on the other hand, no, this isn't a monoculture, where everyone wants the same exact thing. > Discussion and review, particularly with the people who are most familiar with the project (the maintainers) is what makes software better, not worse. Tell that to vim: https://github.com/vim/vim/issues/638 Tell that to node.js: https://github.com/nodejs/node/issues/5798 Tell that to WordPress: https://core.trac.wordpress.org/ticket/21022 https://core.trac.wordpress.org/ticket/25052 etc. Despite all of the time that industry experts have contributed towards identifying and discussing security problems, these projects have severe inertia in the security realm. How much more time do you want us to carve out of our lives for projects that won't fix their problems? > If you're not willing to do that t

https://github.com/nodejs/node/issues/9161 And more specifically, https://github.com/nodejs/node/issues/9161#issuecomment-2545...

Expect a blog post shortly, but from v8 we get these language changes: - await/async behind flag (already covered in thread) - Exponentiation operator: > console.log(60**2*24); 86400 - Object.{values,entries}: > o = { a: 1, b: 2} > Object.values(o); [ 1, 2 ] - Object.getOwnPropertyDescriptor(s): > o = { a: 1 } > Object.getOwnPropertyDescriptors(o); { a: { value: 1, writable: true, enumerable: true, configurable: true } } Additionally, there's a lot of pretty impressive optimization work done by the v8 team. You can read more about that on their blog: http://v8project.blogspot.com Finally, one of my favorite things about Node.js 7.0 is the WhatWG http parser: https://github.com/nodejs/node/pull/7448. edit: elaborated on exponentiation operator

A scheme to generate (and sign) a SHA512 hash that more directly incorporates the full state of the repo was invented, and is used by some projects incl. nodejs https://github.com/cgwalters/git-evtag https://github.com/nodejs/node/issues/7579 I personally think it's overkill

Note that the vm module doesn't protect against local denial-of-service attacks: user-written javascript executed with it could allocate tons of memory or run forever (despite any configured timeouts: https://github.com/nodejs/node/issues/3020).

I guess this use the new (Chromium) debugging API in NodeJS !? https://github.com/nodejs/node/pull/6792

Note that --inspect has issues with Node 6.4+ at the moment: https://github.com/nodejs/node/issues/8155#issuecomment-2504...