Recommend native promises?

[benjamingr]

Given native promises have been up since 2013 I think it would make sense to recommend them over Q with migration notes.

I wouldn't mind writing a package similar to https://github.com/benjamingr/bluebird-api/ for Q if you'd like?

[jbunton-atlassian]

It seems like it would be at least worth mentioning native promises in the README. Personally I wouldn't recommend them over Q though.

In my apps I do global.Promise = q.Promise so that I can use the improved debugging features, primarily long stack traces. I also use extensively use some Q APIs like nfcall which have no equivalent to the native promises.

[benjamingr]

@jbunton-atlassian Node has way better stack traces with async stack traces support in debugging and better unhandled rejection detection, and nfcall can be easily imported independently (or better - something like promisifyAll).

[jbunton-atlassian]

I'm not a fan of promisifyAll, I've seen it break with a semver compatible upgrade when libraries add new methods. But of course you're right that nfcall and friends are easily replaceable.

I'm interested in getting better stack traces for the builtin Node promises. Is this some hidden Node flag, or an npm module that does some magic? In particular can they pass this test ?