Cannot mock relative URLs in v3.0.4

[wheresrhys]

Cannot mock relative URLs in v3.0.4

Getting TypeError: this.realFetch is not a function as well whenever I try to make a POST request in non-testing code

fetch(myApiRoute, {method: 'POST'})

Edit:
Just realized this will work, it needs to have a fetch passed into its context, not the global context.

fetchMock.useNonGlobalFetch(fetch)
fetchMock.mock(myApiRoute, 'POST', payload)

[nanoamp]

I had exactly this problem, using fetch-mock 4.1.1 and isomorphic-fetch 2.2.1. To resolve it I had to do all of the following:

• don't import isomorphic-fetch in the action code (under test). If I did, I always got the only absolute urls error.
• to polyfill for older browsers, import whatwg-fetch; in the action instead.
• in the test class, import isomorphic-fetch; alongside import fetch-mock;

(edited following further simplification)

Hope this helps.

[sstrong-pica9]

@wheresrhys it seems like some people have resolved this issue but I'm doing everything the same and still getting the error from node-fetch:

Error: only absolute urls are supported

The only thing I've noticed about the example from @dr-nick that's different than mine (and I understand it is just a snippet and not full working code) is that it's not testing the response from the async action (using a then statement). Once I try to return the response from the async request, I still get the error, and I don't see a way that error wouldn't be thrown judging by the stack trace and the construct of the Request object.

Sorry to reopen this but I just wanted to know if this was considered resolved or if there was still being more done to solve it.

Here's a snippet of my test that's failing:

describe("async", function() {
    beforeEach(function() {
        fetchMock.useNonGlobalFetch(fetch);
        fetchMock.mock(API_URL, { body: { response: ['value'] }});
    })

    afterEach(function() {
        fetchMock.restore();
    })

    it("runs fetch and collects response", function() {
        const store = mockStore({entities: {}});
        return store.dispatch(actions.action())
            .then(() => {
                expect(true).to.equal(true);
            })
    })
})

[wheresrhys]

I see. So I need to use whatwg-fetch's Request implementation probably. Will have a look in the new year

[wheresrhys]

Or here https://github.com/wheresrhys/fetch-mock/blob/master/src/fetch-mock.js#L65 I can most likely just return a Request-like object as I'm only interested in comparing a few properties, not the internals

[wheresrhys]

fixed in 3.1.1. Cheers for raising the issue

[jwarby]

Thanks for this!

[ericat]

Sorry to open this old issue, but I came across the same error (Error: only absolute urls are supported : Request failed) and I was wondering if you could take a look. I constructed the test exactly as outlined above by jwarby, which is more or less:

import configureMockStore from 'redux-mock-store';
import thunk from 'redux-thunk';
import fetchMock from 'fetch-mock';
import fetch from 'isomorphic-fetch';

/* ... */

global.fetch = fetch;
const middlewares = [thunk];
const mockStore = configureMockStore(middlewares);

describe('actions', () => {
    afterEach(() => {
      fetchMock.restore();
    });

   fetchMock
      .mock('<url>');
});

This is the stack trace:

at Object.assert [as default] (node_modules/expect/lib/assert.js:20:9)
      at Expectation.toEqual (node_modules/expect/lib/Expectation.js:69:26)
      at dispatch (node_modules/redux-mock-store/lib/index.js:55:48)
      at node_modules/redux-thunk/lib/index.js:9:74
      at dispatch (node_modules/redux/lib/applyMiddleware.js:46:18)

I get the same error with nock. I am using fetch-mock 4.1.0 and isomorphic-fetch 2.2.0. The bizarre thing is that I have been advised to use fetch-nock to get around this problem. Am I missing anything obvious?

[wheresrhys]

try importing isomorphic fetch before fetch mock. And you don't need to assign it to a local variable - isomorphic fetch will already set itself as a global

[ericat]

No luck unfortunately :( Thanks for your reply, will probably try to mock the whole thing.

[wheresrhys]

If your code is public on github I don't mind having a look to see what the problem is. There's probably something in the way you're requiring your js that I haven't considered, and which is causing node-fetch to be included instead of whatwg-fetch and I'd like to either fix it or add to the troubleshooting guide.

[ericat]

I'm sure I am. It's not public, but this is basically it:

require('isomorphic-fetch');
import fetchMock from 'fetch-mock';
import configureMockStore from 'redux-mock-store';
import thunk from 'redux-thunk';
import * as actions from '../actions/users';
import {
  LOAD_USERS
} from '../actions/users';

const middlewares = [thunk];
const mockStore = configureMockStore(middlewares);

describe('user actions', () => {
  var user;
  beforeEach(function() {
    contract = {
      name: "Ericat",
      email: "[email protected]"
    };
  });

  afterEach(() => {
    fetchMock.restore();
  });

  it('creates LOAD_USERS', (done) => {
    fetchMock
      .mock('http://127.0.0.1:8080/v1/users', {users: [user]});

    const expectedActions = [
      { type: LOAD_USERS },
      { type: LOAD_USERS, body: { users: [user]  } }
    ];

    const store = mockStore({ users: [] },
      expectedActions,
      done);

      store.dispatch(actions.loadUsers())
  });
});

[ericat]

@dr-nick sorry but I am very confused:

1. by "action code under test", do you mean in the test itself? Because in the last bullet point you seem to be saying the opposite;
2. Do you suggest using whatwg-fetch instead of isomorphic-fetch and calling global.fetch() in my actual code?

Thank you very much for your time

[nanoamp]

@ericat my bad, I'd been through so many permutations trying to make it work that I lost the power of writing!

1. I mean the code being tested - i.e. the redux action creator.
2. I did, although by tweaking the import syntax I've since dropped the need to mess around with explicitly namespacing global, so now only the first part holds true. I've revised the comment to simplify (and lose the confusing last bullet!).

Here's some barebones working code:

fetch.js

import 'whatwg-fetch'; // don't specify `as` or `from` as this polyfills into global namespace anyway
...
export function saveQuery(query) {
  return dispatch => {
    dispatch(storeQuery(query));
    fetch(`SAVE_URL${query}`))
      .then(
        resp => dispatch(receiveResults(resp)),
        error => dispatch(logError(error))
      );
  };
}

FetchTest.js

import configureMockStore from 'redux-mock-store';
import thunk from 'redux-thunk';
import fetchMock from 'fetch-mock';
import 'isomorphic-fetch'; // don't specify `as` or `from` as this polyfills into global namespace anyway
import * as actions from 'actions/fetch';
...
describe('fetch async creators', () => {
  const middlewares = [ thunk ];
  const mockStore = configureMockStore(middlewares);

  afterEach(() => {
    fetchMock.restore();
  });

  it('should dispatch expected actions for saving a query', (done) => {
    fetchMock.mock(/SAVE_URL.+/, {
      savedTerm: true,
    });

    const priorState = {};
    const expectedActions = [
      {
        type: STORE_QUERY,
        query: 'some query',
      }
    ];

    const store = mockStore(priorState, expectedActions, done);
    store.dispatch(actions.saveQuery('some query'));
  });
});

tl;dr: replace isomorphic-fetch with whatwg-fetch in the action creator module alone, make sure you don't assign it to a variable, and you should be golden.

[sallakarppinen]

@ericat, did you ever manage to resolve this issue? I am running into it now with my test suite... @dr-nick's suggestion didn't solve the problem but it did bring about a different error - after reorganising my imports in tests and swapping to whatwg-fetch in my action creators I then got TypeError: this.realFetch is not a function. Does anyone have any further suggestions?

[wheresrhys]

I plan to make the behaviour a bit better anyway. A colleague of mine raised this issue a few days ago too

[giacomorebonato]

The useNonGlobalFetch did the trick for me too, although if in the documentation it is marked as deprecated.

[seethroughdev]

@sstrong-pica9 - did you ever figure this out? I'm still getting the error as well.

[wheresrhys]

Reopening as it's obviously still an ongoing problem. But to investigate I need somebody to post a minimal test case i.e. a repo I can clone, install and attempt to run a test on. It's not an issue I've ever been able to recreate. I have recently (v4.5.4) fixed a bug whereby mocking fetch was not properly scoped to a test/test-group, which may have some bearing on this issue

[seethroughdev]

Thanks @wheresrhys . I'll see if I can extract to a repo this weekend... I am using 4.5.4, and will test with an older version as well. Let you know how it goes.

[seethroughdev]

I think there's too many outside dependencies on my side to confirm this is a fetch-mock issue. (I switched to another fetch mocking utility and got the same result).

Going to dig further, there's definitely an issue, just not sure where its coming from.
Fine to close in the meantime, will comment if I can pinpoint it. Thanks!

[dijs]

I am having the same issues...

"[Error: only absolute urls are supported]"

@dr-nick 's solution worked at first, but then I pulled in https://github.com/redux-effects/redux-effects-fetch and my tests broke with this error again...

[ericat]

@sallakarppinen sorry for the late reply! I am using nock at the moment, everything appears to be working fine. I have put the test in a gist, in case it's useful to someone https://gist.github.com/Ericat/84151d8abdde2e1f228f39bea58b3f04

[killthrush]

I ran into this in v5.0 as well. As far as I can tell, the issue seems to be related to use of a non-global fetch. fetch-mock does not seem to apply to those - is it supposed to? I was able to work around the problem by using global.fetch everywhere. This stack trace helped me find the problem, gathered by using e.stack in my promise's .catch():

 Error: only absolute urls are supported
    at ./node_modules/node-fetch/index.js:54:10
    at new Fetch (./node_modules/node-fetch/index.js:49:9)
    at Fetch (./node_modules/node-fetch/index.js:37:10)
    at module.exports (./node_modules/isomorphic-fetch/fetch-npm-node.js:8:19)
    at callAPI (my-code-under-test.js:37:10)

Note that fetch-mock is nowhere to be found in the trace - my code under test is going straight into the 'real' fetch implementation.

Using mocha 2.4.5, isomorphic-fetch 2.2.1, and fetch-mock 5.0.1.

[wheresrhys]

There are lots of notes on use with non-global fetch here http://www.wheresrhys.co.uk/fetch-mock/installation. If they don't address your problem please provide a minimal test case of your problem (ideally as a repo I can clone, install and attempt to run a test in)

[killthrush]

Oh, I don't actually have a problem anymore, using global everywhere solved it. Was just hoping to help others that ran into the same problem. It's just weird to be using globals again after so long, but that's the fetch standard for you =)

I don't really think it's a bug if fetch is supposed to be global. If however your intent is to make this work even if someone uses an import, then I can probably help. I just need to finish my real work first and I can make a repo.

[wahengchang]

same error, does anyone figure it out ?

I am using NOCK as the API mock tool, and using thunk as async middleware action

[kellyrmilligan]

I can confirm that for me at least, in my entry point to my app,

import 'isomorphic-fetch', and only in the tests where code is involved that calls fetch,

import 'isomorphic-fetch'
import fetchMock from 'fetch-mock'

totally works.