chore(deps): update dependency typescript to v5

[renovate]

closes #481

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typescript (source)	^4.9.4 -> ^5.0.0

---

Release Notes

Microsoft/TypeScript

v5.0.2: TypeScript 5.0

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v5.0.0 (Beta).
• fixed issues query for Typescript v5.0.1 (RC).
• fixed issues query for Typescript v5.0.2 (Stable).

Downloads are available on:

• npm
• NuGet package

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[jasonkuhrt]

In working on this I had to ditch the types we copied over from DOM. It was a bad idea to take that approach. It is not sustainable. Especially now that Node 18+ has global web fetch APIs.

My solution has at least one breaking change for TS users which is that the consumer must now put "lib": ["DOM", "DOM.Iterable", "ES2020”], into their tsconfig.json.

I read this issue DefinitelyTyped/DefinitelyTyped#60924 while solving this. I would consdier that issuse an upstream issue that should be resolved instead of me trying to fight this huge battle alone here on this library.