bluebird

First of all, I know that I have to return promises to avoid this warning. I've also tried returning null as suggested here in the docs . Consider this piece of code, I'm using it in Mongoose's pre-save hook, but I've experienced this warning in other places: var Story = mongoose.model('Story', StorySchema); StorySchema.pre('save', function(next) { var story = this; // Fetch all stories before save to automatically assign // some variable, avoiding conflict with other stories return Story.find().then(function(stories) { // Some code, then set story.somevar value story.somevar = somevar; return

I've come to the realization that since promises in ECMAScript 6 allow for synchronous coding of asynchronous functions, for every promise-laden piece of code there's a synchronous corollary. For instance: var data = processData(JSON.parse(readFile(getFileName()))); Is the same as: var data = getFileName() .then(readFile) .then(JSON.parse) .then(processData); Now for my current use-case I want to write code to pull data from a massive public API. The API is paginated, so in a purely synchronous world I would write something like the following: var data = []; var offset = 0; var total = 10000;

I'm running into a problem where my program ends only on one iteration of the nameList , and I'm not exactly sure where the illogical code lies. Given globally: var _ = require("underscore"); var nameList = ["Bob", "Susie"] var jsonDict = {} My complicated nesting starts here, but I'm not sure how to fix it so that it iterates through both the nameList and the numbers for-loop 1-10 : return new Promise((res, rej) => { var promises = []; return Promise.map(nameList, function(personName){ for (var j=1; j<=10; j++){ return promises.push(new Promise(function(resolve, reject) { params['page'] = j;

Edit: to be more clear - I'm NOT getting warning in example below. I would like to know why and see example code where warning would be printed. In my Node.js project I'm using bluebird Promises library. I observed some cases where I'm getting following warning: Warning: a promise was created in a handler but was not returned from it I understand that the problem occurs when there is promise that is not connected to any promise chain. I'm trying to fully understand how this works and what exactly the problem is in mentioned case. For that purpose I took example from the documentation . Here is

I am creating a node module and I want to be able to support both node callback and Promise APIs. The library that I hear the best things about (mainly that is it the fastest) is bluebird . So after reading some docs and looking at some other libraries that are using bluebird, I thought this would be the cleanest way to get a method to support both node callback and Promise APIs: this.isAllowed = function(role, resource, permission, callback) { var isAllowedAsync = bluebird.promisify(isAllowed); return isAllowedAsync(role, resource, permission).nodeify(callback); }; However with this code, the

In a backend API I have a login route which should perform the following sequence of actions: Given an username and password, try to authenticate the user against an Active Directory. If authentication has failed reply with status 401. If success, continue. Look for an user with the given username in the database. If not found reply with status 403, otherwise continue. Find if the user document has some details like email, display name, etc (in case this is not the first time logging in). If yes reply with the user object, otherwise continue. Get user details from the Active Directory and