Allow URL class object as an argument for fetch()

[Maxim-Mazurok]

Purpose

Fixes #1261

Changes

Added URL to fetch and Request constructor

Additional information

Inspired by: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/a9f480c82b3b356990e5dd574bf2c1ba9c2fdfb5/types/node-fetch/index.d.ts#L213 and https://github.com/microsoft/TypeScript/blob/f43cd0accac3e5033820fd27035731ed88f54938/lib/lib.dom.d.ts#L18281

---

• I added unit test

---

• fix URL is missing in typescript definitions for RequestInfo #1261

[LinusU]

👍

[Maxim-Mazurok]

CI fails for reasons unrelated to the change, it fails with the same errors on the main branch as well.
Following advice from #1657 (comment) adding tsconfig.json with the following contents:

{
	"compilerOptions": {
		"lib": ["DOM"]
	}
}

resolves the issue, however, I'm not sure if that's the correct way to do it.

If it was up to me - I'd force-merge this PR and address the FormData issues separately:

npm run test-types

> node-fetch@3.1.1 test-types
> tsd


  node_modules/formdata-polyfill/esm.min.d.ts:2:10
  ✖    2:10  FormData refers to a value, but is being used as a type here. Did you mean typeof FormData?  
  ✖    3:13  FormData refers to a value, but is being used as a type here. Did you mean typeof FormData?  
  ✖    5:49  FormData refers to a value, but is being used as a type here. Did you mean typeof FormData?  

  @types/index.d.ts:124:3
  ✖  124:3   FormData refers to a value, but is being used as a type here. Did you mean typeof FormData?  
  ✖  137:21  FormData refers to a value, but is being used as a type here. Did you mean typeof FormData?  

  node_modules/fetch-blob/from.d.ts:20:63
  ✖   20:63  File refers to a value, but is being used as a type here. Did you mean typeof File?          
  ✖   25:59  File refers to a value, but is being used as a type here. Did you mean typeof File?          

  node_modules/fetch-blob/file.d.ts:1:75
  ✖    1:75  Element implicitly has an any type because type typeof globalThis has no index signature.    

  8 errors

But happy to add the above mentioned fix if that sounds like a good idea?

[Maxim-Mazurok]

Looking forward to having this published on npm, thanks!

[Maxim-Mazurok]

@jimmywarting, I'm not familiar with the release cycle of this library, but I'm still waiting for this to be published in v3, thank you!

[jimmywarting]

Kind of release a new version every time a PR with the commit fix: or feat: is merged. docs and d.ts is rarely never released

[Maxim-Mazurok]

Ah, I wasn't aware of that... This probably should've been a fix:...
Perhaps adding commitizen or some pre-commit hook to validate commit messages would help new contributors?
I've created a dummy PR with fix: to trigger release now: #1716

[github-actions]

🎉 This PR is included in version 3.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀