I am getting the same error when trying to run tests (using Enzyme and Ava):

Rejected promise returned by test. Reason:

  Error {
    message: 'only absolute urls are supported',
  }

  node_modules/node-fetch/index.js:54:10
  new Fetch (node_modules/node-fetch/index.js:49:9)
  Fetch (node_modules/node-fetch/index.js:37:10)
  node_modules/fetch-ponyfill/fetch-node.js:18:12
  _callee$ (frontend/src/adapters/http.js:28:20)
  makeRequest (frontend/src/adapters/http.js:43:17)
  _callee2$ (frontend/src/adapters/http.js:54:20)

The server don't have an origin so the default domain name is unknown. Therefore relative url won't work. Hence the error.

Supporting file:// protocol is also out of the question.

I would like to close this issue as relative to
#75

Agreed with @jimmywarting. You may want to use new URL(relativeURL, baseURL) to resolve the URL before passing it to node-fetch.

maybe use fetch('http://localhost:3000',...) instead of fetch('/someEndpoint', ...)

@kopax I was having the same issue, it seems to be some issues with the types files. I fixed my issue which was that I was using it like:

fetch({url, headers: {Authorization: `token ${process.GIT_TOKEN}`}})

instead of

fetch(url, {headers: {Authorization: `token ${process.GIT_TOKEN}`}})

Refer: https://stackoverflow.com/a/62512796/1929115

https://codeconqueror.com/blog/get-the-current-url-in-next-js

How would you fix this in nextjs when using getStaticPaths() and getStaticProps() ?

Refer: https://stackoverflow.com/a/62512796/1929115

https://codeconqueror.com/blog/get-the-current-url-in-next-js

that's for next.js only

It looks like there's something wrong with the URL in the fetch method.
For me, it solved by changing url in the fetch method.
Pay attention to the correctness of the URL address.

@Monster880 How did you change the url it to make it work? I am having the same problem.

@dork1

const baseURL = 'http://localhost'
fetch(new URL(url, baseURL))

Thanks @jimmywarting - could you advise what I might be missing?

    function updateDisplayName() {
        const baseURL = 'http://localhost'; // 'http://localhost:8000';
        const url = process.env.AUTHO_POST_ENDPOINT;

    fetch(new URL(url, baseURL, {
        method: 'POST',
        headers: {authorization: 'Bearer ' + process.env.AUTHO_TOKEN},
        data: '{"user_metadata": {"displayName": "FooName"}',
    }))
        .then(function(response) {
            console.log('update', response.data);
        }).catch(function(error) {
            console.error(error);
        });
    };

response.data is wrong use response.body instead if you intend to use the response stream and pipe it
if you need to get the response data then you need to call either

• await response.json(),
• await response.text() or
• await response.arrayBuffer()

there is nothing in the spec that defines .data

same with request body: it should be

    fetch(new URL(url, baseURL, {
        method: 'POST',
        headers: {authorization: 'Bearer ' + process.env.AUTHO_TOKEN},
-        data: '{"user_metadata": {"displayName": "FooName"}',
+        body: '{"user_metadata": {"displayName": "FooName"}',
    }))

@jimmywarting Thank you! I am now getting a response!

Would be nice if the error message saying only absolute urls are supported included the actual URL and consequentially spared a bit of headache for the users