Adapters do not work with custom context.

The fetch adapter supports an option called context, which allows you to configure where the adapter will look for a fetch object to replace. However, this doesn’t work: updating the context object doesn’t do anything, because the object is a clone.

As a workaround, I’m currently using:

const polly = new Polly(recordingName, {
  // ...
  adapterOptions: {
    fetch: {
      context: fetchContext,
    }
  }
});
fetchContext.fetch = polly.config.adapterOptions.fetch.context.fetch;

[CGamesPlay]

Thanks for the quick turnaround, everyone!

[CGamesPlay]

I wouldn’t bemoan if the library were hard-coded to use the global context. I did end up needing to patch some bugs in node-fetch for use in my test environment, so I overrode the global Response and Headers classes, but I could just as easily do that if they were on the global object.

I should add, I only went down this path because the library advertised it as an option.