Adam Crabtree

Stumbled upon this. There's likely another root cause, but for a band-aid, see increasing the V8 stack size options: ``` node --stack_size=4096 index.js ``` https://groups.google.com/group/nodejs-dev/browse_thread/thread/2b206819302ad5c4

Sure, but not ATM. Perhaps in the coming month. Feel free to ping me here if I forget.

https://github.com/trayio/babel-plugin-webpack-alias/pull/57 >Upgrade to Babel 7

Resolution: See https://github.com/tlrobinson/long-stack-traces/issues/9#issuecomment-10214092

Yes. It's super annoying. I don't know why that is, but the whole toolchain is rather obtuse. I'm going to try and set the breakpoint through the front-end instead of...

@Qard It at least has the benefit of not having to solve these problems itself. Others will both solve and experience the pain first.

@mikeal I hear you and echo most[1] of your perspective. This issue is not about language features being de facto idiomatic. It's about avoiding a node-flavored versions when language-first versions...

@bmeck @rlidwka @chrisdickinson @vkurchatkin =) Lots of constructive feedback makes me happy. @chrisdickinson > I would heartily suggest avoiding teaching newcomers that inheritance is the proper way to interact with...

@bmeck Why can't that be written with `async/await`? ``` node async foo(abort) { let release = await lockfile('filename.lock', abort); try { db.query(...); fs.write('filename', ...); ... } finally { release(); }...

@bmeck Ah. This is very interesting, and as you say "complex". Equivalent functionality could only be accomplished by checking compromised at every call to `await`, and it's the manual control...