How do I promisify native XHR?

问题:

I want to use (native) promises in my frontend app to perform XHR request but without all the tomfoolery of a massive framework.

I want my xhr to return a promise but this doesn\'t work (giving me: Uncaught TypeError: Promise resolver undefined is not a function)

function makeXHRRequest (method, url, done) {
  var xhr = new XMLHttpRequest();
  xhr.open(method, url);
  xhr.onload = function() { return new Promise().resolve(); };
  xhr.onerror = function() { return new Promise().reject(); };
  xhr.send();
}

makeXHRRequest(\'GET\', \'http://example.com\')
.then(function (datums) {
  console.log(datums);
});

回答1:

I\'m assuming you know how to make a native XHR request (you can brush up here and here)

Since any browser that supports native promises will also support xhr.onload, we can skip all the onReadyStateChange tomfoolery. Let\'s take a step back and start with a basic XHR request function using callbacks:

function makeRequest (method, url, done) {
  var xhr = new XMLHttpRequest();
  xhr.open(method, url);
  xhr.onload = function () {
    done(null, xhr.response);
  };
  xhr.onerror = function () {
    done(xhr.response);
  };
  xhr.send();
}

// And we\'d call it as such:

makeRequest(\'GET\', \'http://example.com\', function (err, datums) {
  if (err) { throw err; }
  console.log(datums);
});

Hurrah! This doesn\'t involve anything terribly complicated (like custom headers or POST data) but is enough to get us moving forwards.

The promise constructor

We can construct a promise like so:

new Promise(function (resolve, reject) {
  // Do some Async stuff
  // call resolve if it succeeded
  // reject if it failed
});

The promise constructor takes a function that will be passed two arguments (let\'s call them resolve and reject). You can think of these as callbacks, one for success and one for failure. Examples are awesome, let\'s update makeRequest with this constructor:

function makeRequest (method, url) {
  return new Promise(function (resolve, reject) {
    var xhr = new XMLHttpRequest();
    xhr.open(method, url);
    xhr.onload = function () {
      if (this.status >= 200 && this.status < 300) {
        resolve(xhr.response);
      } else {
        reject({
          status: this.status,
          statusText: xhr.statusText
        });
      }
    };
    xhr.onerror = function () {
      reject({
        status: this.status,
        statusText: xhr.statusText
      });
    };
    xhr.send();
  });
}

// Example:

makeRequest(\'GET\', \'http://example.com\')
.then(function (datums) {
  console.log(datums);
})
.catch(function (err) {
  console.error(\'Augh, there was an error!\', err.statusText);
});

Now we can tap into the power of promises, chaining multiple XHR calls (and the .catch will trigger for an error on either call):

makeRequest(\'GET\', \'http://example.com\')
.then(function (datums) {
  return makeRequest(\'GET\', datums.url);
})
.then(function (moreDatums) {
  console.log(moreDatums);
})
.catch(function (err) {
  console.error(\'Augh, there was an error!\', err.statusText);
});

We can improve this still further, adding both POST/PUT params and custom headers. Let\'s use an options object instead of multiple arguments, with the signature:

{
  method: String,
  url: String,
  params: String | Object,
  headers: Object
}

makeRequest now looks something like this:

function makeRequest (opts) {
  return new Promise(function (resolve, reject) {
    var xhr = new XMLHttpRequest();
    xhr.open(opts.method, opts.url);
    xhr.onload = function () {
      if (this.status >= 200 && this.status < 300) {
        resolve(xhr.response);
      } else {
        reject({
          status: this.status,
          statusText: xhr.statusText
        });
      }
    };
    xhr.onerror = function () {
      reject({
        status: this.status,
        statusText: xhr.statusText
      });
    };
    if (opts.headers) {
      Object.keys(opts.headers).forEach(function (key) {
        xhr.setRequestHeader(key, opts.headers[key]);
      });
    }
    var params = opts.params;
    // We\'ll need to stringify if we\'ve been given an object
    // If we have a string, this is skipped.
    if (params && typeof params === \'object\') {
      params = Object.keys(params).map(function (key) {
        return encodeURIComponent(key) + \'=\' + encodeURIComponent(params[key]);
      }).join(\'&\');
    }
    xhr.send(params);
  });
}

// Headers and params are optional
makeRequest({
  method: \'GET\',
  url: \'http://example.com\'
})
.then(function (datums) {
  return makeRequest({
    method: \'POST\',
    url: datums.url,
    params: {
      score: 9001
    },
    headers: {
      \'X-Subliminal-Message\': \'Upvote-this-answer\'
    }
  });
})
.catch(function (err) {
  console.error(\'Augh, there was an error!\', err.statusText);
});

A more comprehensive approach can be found at MDN.

Alternatively, you could use the fetch API (polyfill).

回答2:

This could be as simple as the following code.

Keep in mind that this code will only fire the reject callback when onerror is called (network errors only) and not when the HTTP status code signifies an error. This will also exclude all other exceptions. Handling those should be up to you, IMO.

Additionally, it is recommended to call the reject callback with an instance of Error and not the event itself, but for sake of simplicity, I left as is.

function request(method, url) {
    return new Promise(function (resolve, reject) {
        var xhr = new XMLHttpRequest();
        xhr.open(method, url);
        xhr.onload = resolve;
        xhr.onerror = reject;
        xhr.send();
    });
}

And invoking it could be this:

request(\'GET\', \'http://google.com\')
    .then(function (e) {
        console.log(e.target.response);
    }, function (e) {
        // handle errors
    });

回答3:

For anyone who searches for this now, you can use the fetch function. It has some pretty good support.

I\'ve firstly used @SomeKittens\'s answer, but then discovered fetch that does it for me out of the box :)

回答4:

I think we can make the top answer much more flexible and reusable by not having it create the XMLHttpRequest object. The only benefit of doing so is that we don\'t have to write 2 or 3 lines of code ourselves to do it, and it has the enormous drawback of taking away our access to many of the API\'s features, like setting headers. It also hides properties of the original object from the code that\'s supposed to handle the response (for both successes and errors). So we can make a more flexible, more widely applicable function by just accepting the XMLHttpRequest object as input and passing it as the result.

This function converts an arbitrary XMLHttpRequest object into a promise, treating non-200 status codes as an error by default:

function promiseResponse(xhr, failNon2xx = true) {
    return new Promise(function (resolve, reject) {
        // Note that when we call reject, we pass an object
        // with the request as a property. This makes it easy for
        // catch blocks to distinguish errors arising here
        // from errors arising elsewhere. Suggestions on a 
        // cleaner way to allow that are welcome.
        xhr.onload = function () {
            if (failNon2xx && (xhr.status < 200 || xhr.status >= 300)) {
                reject({request: xhr});
            } else {
                resolve(xhr);
            }
        };
        xhr.onerror = function () {
            reject({request: xhr});
        };
        xhr.send();
    });
}

This function fits very naturally into a chain of Promises, without sacrificing the flexibility of the XMLHttpRequest API:

Promise.resolve()
.then(function() {
    // We make this a separate function to avoid
    // polluting the calling scope.
    var xhr = new XMLHttpRequest();
    xhr.open(\'GET\', \'https://stackoverflow.com/\');
    return xhr;
})
.then(promiseResponse)
.then(function(request) {
    console.log(\'Success\');
    console.log(request.status + \' \' + request.statusText);
});

catch was omitted above to keep the sample code simpler. You should always have one, and of course we can:

Promise.resolve()
.then(function() {
    var xhr = new XMLHttpRequest();
    xhr.open(\'GET\', \'https://stackoverflow.com/doesnotexist\');
    return xhr;
})
.then(promiseResponse)
.catch(function(err) {
    console.log(\'Error\');
    if (err.hasOwnProperty(\'request\')) {
        console.error(err.request.status + \' \' + err.request.statusText);
    }
    else {
        console.error(err);
    }
});

And disabling the HTTP status code handling doesn\'t require much change in the code:

Promise.resolve()
.then(function() {
    var xhr = new XMLHttpRequest();
    xhr.open(\'GET\', \'https://stackoverflow.com/doesnotexist\');
    return xhr;
})
.then(function(xhr) { return promiseResponse(xhr, false); })
.then(function(request) {
    console.log(\'Done\');
    console.log(request.status + \' \' + request.statusText);
});

Our calling code is longer, but conceptually, it\'s still simple to understand what\'s going on. And we don\'t have to rebuild the entire web request API just to support its features.

We can add a few convenience functions to tidy up our code, as well:

function makeSimpleGet(url) {
    var xhr = new XMLHttpRequest();
    xhr.open(\'GET\', url);
    return xhr;
}

function promiseResponseAnyCode(xhr) {
    return promiseResponse(xhr, false);
}

Then our code becomes:

Promise.resolve(makeSimpleGet(\'https://stackoverflow.com/doesnotexist\'))
.then(promiseResponseAnyCode)
.then(function(request) {
    console.log(\'Done\');
    console.log(request.status + \' \' + request.statusText);
});

回答5:

jpmc26\'s answer is quite close to perfect in my opinion. It has some drawbacks, though:

1. It exposes the xhr request only until the last moment. This does not allow POST-requests to set the request body.
2. It is harder to read as the crucial send-call is hidden inside a function.
3. It introduces quite a bit of boilerplate when actually making the request.

Monkey patching the xhr-object tackles these issues:

function promisify(xhr, failNon2xx=true) {
    const oldSend = xhr.send;
    xhr.send = function() {
        const xhrArguments = arguments;
        return new Promise(function (resolve, reject) {
            // Note that when we call reject, we pass an object
            // with the request as a property. This makes it easy for
            // catch blocks to distinguish errors arising here
            // from errors arising elsewhere. Suggestions on a 
            // cleaner way to allow that are welcome.
            xhr.onload = function () {
                if (failNon2xx && (xhr.status < 200 || xhr.status >= 300)) {
                    reject({request: xhr});
                } else {
                    resolve(xhr);
                }
            };
            xhr.onerror = function () {
                reject({request: xhr});
            };
            oldSend.apply(xhr, xhrArguments);
        });
    }
}

Now the usage is as simple as:

let xhr = new XMLHttpRequest()
promisify(xhr);
xhr.open(\'POST\', \'url\')
xhr.setRequestHeader(\'Some-Header\', \'Some-Value\')

xhr.send(resource).
    then(() => alert(\'All done.\'),
         () => alert(\'An error occured.\'));

Of course, this introduces a different drawback: Monkey-patching does hurt performance. However this should not be a problem assuming that the user is waiting mainly for the result of the xhr, that the request itself takes orders of magnitude longer than setting up the call and xhr requests not being sent frequently.

PS: And of course if targeting modern browsers, use fetch!