title: Is there a way to bypass node-fetch res.text() to get a raw response body?
body: <p>I'm having node-fetch issues.  An API that I can access perfectly fine in POSTMAN throws the same error using node-fetch and I cannot get it to spit out a response body.  I know there must be one and I have theories why it's likely improperly formatted.</p>
  <p>Here is my code.</p>
  <pre><code>fetch(`apiUrl`, options)
      .then((res) =&gt; {
          console.log(res);
          return res.text();
          })
      .then((res) =&gt; {
          console.log(res);
          })
      .catch((err) =&gt; {
          console.log(err);
          }); 
  </code></pre>
  <p>This code never prints a response body event after calling res.text().  My question is there another way to get to the RAW response body other than call .text() so that I can see if the API is responding.  It's responding with a status:200 and I'm fairly certain there is a body because when I cURL from PHP and request from POSTMAN I get the expected response body.</p>
  <p>The errors is always:</p>
  <p>FetchError: invalid response body at: apiUrl reason: unexpected end of file</p>