I just want a version that reliably produces stack traces that include a line of my code somewhere. I too often get some crash that has a random line from the guts of Node and nothing else. I often have to resort to putting log statements all over just to figure out what line caused the crash.

Totally understandable if its not possible, but if the error is in a package for example, RunKit might be a big help. We've put a ton of work in making great stack traces: http://blog.runkit.com/2017/02/01/stop-filing-bugs-file-a-co...

shameless plug: https://github.com/AriaMinaei/pretty-error

It allows you to abbreviate stack traces, ignore non-relevant modules, etc.

This is a fantastic decision imo. I like how "consumer and developer" driven they are being with this so as to have up to date deps.

I see this as waiting 2 months for a updated product line instead of jumping the gun on buying a MacBook Pro right this minute .

To someone not familiar with the internals of V8 and its roadmap, this seems like a sound (albeit unfortunately timed) decision.

So I believe this will also mean WebAssembly on by default. It'll be interesting to see what impacts that has.

>The LTS release date remains in October, unaffected by this delay.