Support `fetch` API

[cnuss]

Hi there!

Could we get fetch support?

Assuming the following index.js:

(async () => {
  const response = await fetch("https://api.github.com/users/cnuss");
  const data = await response.json();
  console.log(data.url);
})();

The output of npx porffor index.js -d is:

npx porffor index.js -d
name (ByteString) | 285 (1d 01 00 00)
  value: ReferenceError (ByteString) | 6661 (00 00 00 00 00 05 ba 40)
  flags: 0b1110 0e c3
    accessor: false
    configurable: true
    enumerable: true
    writable: true

message (ByteString) | 402 (92 01 00 00)
  value: fetch is not defined (in #anonymous_0) (ByteString) | 9616 (00 00 00 00 00 c8 c2 40)
  flags: 0b1110 0e c3
    accessor: false
    configurable: true
    enumerable: true
    writable: true

constructor (ByteString) | 320 (40 01 00 00)
  value: [name]() {} (Function) | 40 (00 00 00 00 00 00 44 40)
  flags: 0b1110 0e 06
    accessor: false
    configurable: true
    enumerable: true
    writable: true

Current porffor version:

npx porffor --help
Porffor is a JavaScript/TypeScript engine/compiler/runtime. (0.50.23)

[riziles]

@cnuss, stop trying to make fetch happen. It’s not going to happen.

[christiannuss-ybor]

@riziles FYI: @CanadaHonk asked for a issue to be made in the Discord

[riziles]

@cnuss, wait. Have you not seen mean girls?

[christiannuss-ybor]

OMG that went right over my head and I will never forget mean girls again

[andriemc]

Porffor is probably not gonna have something like fetch out of the box, all it has and probably will have by default is libc apis and let libraries do the rest

[riziles]

Well, crap, @christiannuss-ybor. Now I feel like an a**. I'm sorry.