I am looking for a way, with Node v7.6 or above, to get a Bluebird Promise (or any non-native promise) when an async function is called.
In the same way I can do:
global.Promise = require('Bluebird'); // Or Q/When
var getResolvedPromise = () => Promise.resolve('value');
getResolvedPromise
.tap(...) // Bluebird method
.then(...);
See: May I use global.Promise=require("bluebird")
I want to be able to do something like:
global.Promise = require('Bluebird'); // Or Q/When
var getResolvedAsyncAwaitPromise = async () => 'value';
getResolvedAsyncAwaitPromise()
.tap(...) // Error ! Native Promises does not have `.tap(...)`
.then(...);
I know I can use at any moment something like:
Bluebird.resolve(getResolvedAsyncAwaitPromise())
.tap(...);
But I was curious if there would be a way to change the default Promise returned by AsyncFunction
. The constructor seems enclosed:
Note that AsyncFunction is not a global object. It could be obtained by evaluating the following code.
Object.getPrototypeOf(async function(){}).constructor
MDN reference on AsyncFunction
If there is no way to change the AsyncFunction
's Promise constructor, I would like to know the reasons of this locking.
Thank you !
Yes. You can do it even simpler with Bluebird than in your example: let fs = Promise. promisifyAll(require('fs')); // and in async function: let contents = await fs.
Async functions always return a promise. If the return value of an async function is not explicitly a promise, it will be implicitly wrapped in a promise.
Yes, you can use Promise chains instead of async/await , but this way is more verbose: fixture`MyFixture` .
1. Promise is an object representing intermediate state of operation which is guaranteed to complete its execution at some point in future. Async/Await is a syntactic sugar for promises, a wrapper making the code execute more synchronously.
Is there a way to change the default Promise returned by AsyncFunction
No.
What are the reasons of this locking
The ability to hijack all async function
s could be a security issue. Also, even where that is no problem, it's still not useful to do this replacement globally. It would affect your entire realm, including all libraries that you are using. They might rely on using native promises. And you cannot use two different promise libraries, although they might be required.
I want to be able to do something like:
getResolvedAsyncAwaitPromise().tap(...)
What you can do is to wrap the function at its definition with Promise.method
:
const Bluebird = require('Bluebird');
const getResolvedAsyncAwaitPromise = Bluebird.method(async () => 'value');
getResolvedAsyncAwaitPromise()
.tap(…) // Works!
.then(…);
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With