'body used already for' error when mocking node fetch?

Question

I'm trying to mock node-fetch with jest for my azure functions. In the test I have the following:

index.test.ts

jest.mock("node-fetch");
import fetch from "node-fetch";
const {Response} = jest.requireActual("node-fetch");

// Setup code here...

const expectedResult: User = {
        user_id: "1",
        email: "testEmail@email.com",
        name: "testUser",
        nickname: "test",
        picture: "pic",
        app_metadata: {
            email: "testEmail@email.com"
        }
    };
    (fetch as jest.MockedFunction<typeof fetch>).mockReturnValue(new Response(JSON.stringify(expectedResult)));

When I call it I'm doing the following:

index.ts


const options = {
                method: 'PATCH',
                headers: { "Content-Type": 'application/json', authorization: `Bearer ${accessToken}`},
                body: body
            };

const userResponse = await fetch(usersEndpoint, options);
const jsonResult = await userResponse.json();
context.res = {
                body: jsonResult
            };

When it hits the "await userResponse.json()" I get "body used already for" error. I have another test that is set up in a similar manner which works so I'm not sure why it's saying the body is used up from the await fetch call. Any help would be appreciated.

score 5 · Answer 1 · edited May 12 '23 at 21:34

5

Response object is supposed to be used once per request while mocked fetch returns the same object for multiple requests. Also, it should return a promise of a response, not a response itself.

A correct way to mock it is:

fetch.mockImplementation(() => Promise.resolve(
  new Response(JSON.stringify(expectedResult))
));

It's unnecessary to use Response and follow the restrictions it imposes, especially since there's no native Response in Node.

It can be:

fetch.mockResolvedValue({
  json: jest.fn(() => expectedResult)
});

edited May 12 '23 at 21:34

jedmao

10,224
11
59
65

answered Jul 29 '20 at 13:59

Estus Flask

206,104
70
425
565

This worked for me, but my problem ended up being that I had a call to fetch earlier in the function that was resolving the mock value. My syntax ended up working once I mocked the return value of this other call instead of using the implementation. – avenmia Jul 29 '20 at 14:27

score 0 · Answer 2 · answered Jul 29 '20 at 14:29

My problem was I had a call to another function that used fetch which was resolving my mock implementation. Once I mocked that return value:

 (fetch as jest.MockedFunction<typeof fetch>).mockReturnValue(new Response(JSON.stringify(expectedResult)));

ended up working.

@Estus Flask's answer also ended up working.

'body used already for' error when mocking node fetch?

2 Answers2