Should nodeify handle additional parameters for callbacks

I asked a question on StackOverflow seeking help with dealing with the callback for a passport.js strategy callback.

The strategy callback allows an optional parameter which can be used as a flash message.

// This strategy is used by passport to handle logins
module.exports.localStrategy = new LocalStrategy(function(username, password, done) {
  users.findOneAsync({username: username}).bind({})
    .then(function(user) {
        if (!user) {
          throw new NoMatchedUserError('Incorrect username.');
          //should be equivalent to:
          // return done(null, false, {message:'something'});
        }
        this.user = user;
        return compare(password, user.password);
    })
    .then(function(isMatch) {
      if (isMatch) {
        return this.user;
        //is equivalent to:
        // return done(null, this.user);
      }
      else {
        throw { message: 'Incorrect password.' };
        //should be equivalent to:
        // return done(null, false, {message:'something else'};
      }
    })
    .nodeify(done);
});

Benjamin Gruenbaum suggested on that question that this might be a feature worth adding in

My JS chops fall way short of knowing where to start on implementing this so apologies for suggesting work for others! Really interested to watch commits to see the shape this might take…

[petkaantonov]

Implemented for 2.0

[petkaantonov]

Promise.resolve([1,2,3]).nodeify(function(err, a, b, c) {
    // a is [1,2,3]
    // b is undefined
    // c is undefined
})

Promise.resolve([1,2,3]).nodeify(function(err, a, b, c) {
    // a is 1
    // b is 2
    // c is 3
}, {spread: true})