195

I've been messing around with the fetch() api recently, and noticed something which was a bit quirky.

let url = "http://jsonplaceholder.typicode.com/posts/6";

let iterator = fetch(url);

iterator
  .then(response => {
      return {
          data: response.json(),
          status: response.status
      }
  })
  .then(post => document.write(post.data));
;

post.data returns a Promise object. http://jsbin.com/wofulo/2/edit?js,output

However if it is written as:

let url = "http://jsonplaceholder.typicode.com/posts/6";

let iterator = fetch(url);

iterator
  .then(response => response.json())
  .then(post => document.write(post.title));
;

post here is a standard Object which you can access the title attribute. http://jsbin.com/wofulo/edit?js,output

So my question is: why does response.json return a promise in an object literal, but return the value if just returned?

Mike Lyons
  • 1,706
  • 2
  • 20
  • 33
haveacigaro
  • 2,091
  • 2
  • 12
  • 8
  • 3
    This makes sense when you consider the `response.json()` promise might be rejected if the response is not valid JSON. – ssube May 31 '16 at 20:37
  • 1
    The value is returned because promise has been resolved passing the value in response.json(). Now the value is available in then method. – Jose Hermosilla Rodrigo May 31 '16 at 20:41
  • Does this answer your question? [Why is the response object from JavaScript fetch API a promise?](https://stackoverflow.com/questions/32721850/why-is-the-response-object-from-javascript-fetch-api-a-promise) – Josh Correia Apr 01 '21 at 21:23
  • 1
    Note that despite the method being named json(), the result is not JSON. It returns a promise which resolves with a JavaScript object that is the result of parsing the body text as JSON. This object could be anything that can be represented by JSON — an object, an array, a string, a number... reference: https://developer.mozilla.org/en-US/docs/Web/API/Body/json – Nasim B. D Apr 24 '21 at 05:15
  • https://stackoverflow.com/a/65445674/470749 was the most helpful answer for me so far. – Ryan May 15 '21 at 23:49

6 Answers6

239

Why does response.json return a promise?

Because you receive the response as soon as all headers have arrived. Calling .json() gets you another promise for the body of the http response that is yet to be loaded. See also Why is the response object from JavaScript fetch API a promise?.

Why do I get the value if I return the promise from the then handler?

Because that's how promises work. The ability to return promises from the callback and get them adopted is their most relevant feature, it makes them chainable without nesting.

You can use

fetch(url).then(response => 
    response.json().then(data => ({
        data: data,
        status: response.status
    })
).then(res => {
    console.log(res.status, res.data.title)
}));

or any other of the approaches to access previous promise results in a .then() chain to get the response status after having awaited the json body.

robsch
  • 8,936
  • 8
  • 58
  • 92
Bergi
  • 572,313
  • 128
  • 898
  • 1,281
  • 1
    It seems weird that I can't just wait for the data to return using a Promise, and when it's arrived convert it to json? Or perhaps in that case I could just use `JSON.parse()` instead of `res.json()` ?? – Kokodoko Nov 17 '17 at 13:12
  • 15
    @Kokodoko `res.json()` basically is a shortcut for `res.text().then(JSON.parse)`. Both wait for the data using a promise and parse the json. – Bergi Nov 17 '17 at 13:15
  • @Bergi, hi, sorry I faced some confusion, that is, by using then(res=>res.json()) we send another request to get JSON? – mirzhal Jun 13 '19 at 12:17
  • 2
    @mirzhal No, there is no other request. It just is reading (asynchronously!) the rest of the response. – Bergi Jun 13 '19 at 20:08
25

This difference is due to the behavior of Promises more than fetch() specifically.

When a .then() callback returns an additional Promise, the next .then() callback in the chain is essentially bound to that Promise, receiving its resolve or reject fulfillment and value.

The 2nd snippet could also have been written as:

iterator.then(response =>
    response.json().then(post => document.write(post.title))
);

In both this form and yours, the value of post is provided by the Promise returned from response.json().


When you return a plain Object, though, .then() considers that a successful result and resolves itself immediately, similar to:

iterator.then(response =>
    Promise.resolve({
      data: response.json(),
      status: response.status
    })
    .then(post => document.write(post.data))
);

post in this case is simply the Object you created, which holds a Promise in its data property. The wait for that promise to be fulfilled is still incomplete.

Jonathan Lonowski
  • 117,332
  • 31
  • 195
  • 197
7

Also, what helped me understand this particular scenario that you described is the Promise API documentation, specifically where it explains how the promised returned by the then method will be resolved differently depending on what the handler fn returns:

if the handler function:

  • returns a value, the promise returned by then gets resolved with the returned value as its value;
  • throws an error, the promise returned by then gets rejected with the thrown error as its value;
  • returns an already resolved promise, the promise returned by then gets resolved with that promise's value as its value;
  • returns an already rejected promise, the promise returned by then gets rejected with that promise's value as its value.
  • returns another pending promise object, the resolution/rejection of the promise returned by then will be subsequent to the resolution/rejection of the promise returned by the handler. Also, the value of the promise returned by then will be the same as the value of the promise returned by the handler.
Gera Zenobi
  • 1,078
  • 11
  • 7
6

In addition to the above answers here is how you might handle a 500 series response from your api where you receive an error message encoded in json:

function callApi(url) {
  return fetch(url)
    .then(response => {
      if (response.ok) {
        return response.json().then(response => ({ response }));
      }

      return response.json().then(error => ({ error }));
    })
  ;
}

let url = 'http://jsonplaceholder.typicode.com/posts/6';

const { response, error } = callApi(url);
if (response) {
  // handle json decoded response
} else {
  // handle json decoded 500 series response
}
jcroll
  • 6,459
  • 9
  • 50
  • 61
-1

The json() method is available on all fetch() function. The json() method returns a Promise. Remember, when returning a Promise, it is still pending because it is asynchronous (assuming the data is not there yet). So to get the data AFTER using the json() method, you need to use another then() method so it will just return the data after it arrives.

To answer your question, It is what it is, its just the way of doing that.

Its like Promise ---> Another Promise ----> data

Zowy
  • 23
  • 7
-3

Use await with responce.json() also

const responce = await fetch(url);
const result = await responce.json();

Use await with responce.json() also