Meteor methods - Promise on server side

[XTA]

Hey,
assuming I’m having the following Meteor method:

server/methods.js

'test': function() {

    return new Promise((resolve) => {
       setTimeout(() => {resolve(true);},10000);
    });
}

server/test.js

Meteor.call('test',(err,res) => {console.log(res)});

The problem is, that the callback is called immediately without waiting for the Promise. As response I only get a {}.If I do the same on client side

client/test.js

Meteor.call('test',(err,res) => {console.log(res)});

everything is working fine. Why does a Promise method don’t work on server side? I’ve already tried https://github.com/deanius/meteor-promise/, but this one is also not working (I guess it’s client side only if I take a look into the package.js).

Is there any workaround or package? Currently I have to wrap our async function with Meteor.wrapAsync but it would be cool if I could remove it and replace it with some ES6 stuff

[n1s]

Hey,

You should have a look here

Promises/async/await in Meteor

There have been a number of forum posts recently around the topic of working with Promises in Meteor. I’ve put together a short Medium article on server-side Promises and how they interact with Meteor’s classic Fiber-based coding, including mixing 3rd party Promises with Meteor Promises. I’m not 100% sure that Medium is the best tool for technical articles, but here it is anyway. Feedback welcomed!

[XTA]

@n1s Yeah, I’ve read this great article already. The problem is that it shows the typical client<->server case where Promises work fine. In my case, I do a server<->server method call - there I get an empty response within the callback.

@robfallows any idea why server<->server doesn’t work (example above)?

[tomsp]

@XTA you can try const promise = someFunctionThatReturnsAPromise(); return promise.await(); similar to what i posted here: Nightmarejs inside meteor Can't return method result

Let me know if it works for you.

[n1s]

You can use the synchronous version of Meteor.call and use Promise.await(...) to make your promise synchronous

[XTA]

@tomsp Thank you man, this way it works

[robfallows]

@XTA

@robfallows any idea why server<->server doesn’t work (example above)?

I discovered this behaviour a while ago, but didn’t make a repro. I’m going to do that today and raise an issue if needed.

EDIT: Issue raised:

Server side call to async method returns Promise object, not value.