feat!: app.request

[pi0]

Followup on #1096 with app.fetch(req) becoming more restricted, it makes sense we make app.request(req, init, ctx) a public API to unblock DX limits.

Other API change: Types are now Response | Promise<Response> to reduce unnecessary wrappings. (please comment if anyone feels this is a bad DX)

[cloudflare-workers-and-pages]

Deploying h3dev with    Cloudflare Pages

Latest commit:	1344e7d
Status:	✅  Deploy successful!
Preview URL:	https://117d2cd8.h3dev.pages.dev
Branch Preview URL:	https://feat-app-req.h3dev.pages.dev

View logs

[codecov]

Codecov Report

❌ Patch coverage is 57.89474% with 8 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/_entries/bun.ts	0.00%	1 Missing ⚠️
src/_entries/cloudflare.ts	0.00%	1 Missing ⚠️
src/_entries/deno.ts	0.00%	1 Missing ⚠️
src/_entries/generic.ts	0.00%	1 Missing ⚠️
src/_entries/node.ts	0.00%	1 Missing ⚠️
src/_entries/service-worker.ts	0.00%	1 Missing ⚠️
src/adapters.ts	0.00%	1 Missing ⚠️
src/utils/proxy.ts	50.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[huseeiin]

yes i think it should be Promise<Response> to match globalThis.fetch. imagine someone making an SSR framework and they override globalThis.fetch so it works like SPA (similar to nuxt useFetch, P.S. i know useFetch is not overriding globalThis.fetch). users then will use fetch("/route").then(res => res.json()) and get fetch("/route").then is undefined error

[pi0]

Wrappers can easily use Promise.resolve() when overriding globalThis.fetch to match.