fix(deps): update dependency isomorphic-unfetch to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
isomorphic-unfetch	3.1.0 -> 4.0.2

---

Release Notes

developit/unfetch (isomorphic-unfetch)

v4.0.2

Compare Source

v4.0.1

Compare Source

Quick publishing fix.

v4.0.0

Compare Source

🦄 Small breaking change for awesome ponyness:

• unfetch is now a pure ponyfill.
• unfetch/polyfill is now the polyfill version (even smaller than the ponyfill!)
• All modules are shipped in all formats, and the polyfill is now < 500b.
• Also a little bugfix for IE11 (#​85, thanks @​khusa)

TL;DR: require('unfetch') no longer returns window.fetch when it exists. For that, use unfetch/polyfill.

This change makes unfetch lovely to use as a polyfill from HTML:

<script src="https://unpkg.com/unfetch/polyfill"></script>
<!-- that's it! -->
<script>foo = await fetch('/foo.json')</script>

Otherwise, if you're using Unfetch and bundling your code, continue as you were before:

if (!self.fetch) self.fetch = require('unfetch');
// or simply:
import 'unfetch/polyfill';

Important - the one thing to avoid:

Since unfetch is a proper ponyfill, it will now overwrite fetch even in supported browsers if you do the following

// never do this!
window.fetch = require('unfetch');

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json