Thread

1. franciscop · 1790842468 · focus · HN ↗

   If someone in Netlify is listening, could you please add support for Fetchable[1] in Netlify Edge Functions? I opened a ticket 1 week ago but it has gone unanswered[2].

   The idea behind Fetchable is to have a (semi) standard across runtimes and environments to be able to do this:

       export default {
         async fetch(req: Request): Promise<Response> {
           return new Response(`Hello, ${req.headers.get("User-Agent")}!`)
         }
       }
   

   Even Node.js, who are traditionally the laggards in these things, are already working on it and implementing it. This would be very useful for library writers like me to be able to standardize code across envrionments. I'm re-writing npm's `server` (currently WIP here [3]) and I have some ugly workarounds ONLY for Netlify Edge Functions.

   [1] <a href="https:&#x2F;&#x2F;fetchable.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;fetchable.org&#x2F; [2] <a href="https:&#x2F;&#x2F;answers.netlify.com&#x2F;t&#x2F;support-fetch-for-netlify-edge-functions&#x2F;170521" rel="nofollow">https:&#x2F;&#x2F;answers.netlify.com&#x2F;t&#x2F;support-fetch-for-netlify-edge... [3] <a href="https:&#x2F;&#x2F;server-js.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;server-js.com&#x2F;

   1. pjmlp · 1790845521 · focus · HN ↗

      Even better, catch up with everyone else and support containers on serverless infrastructure.

Unofficial Hacker News client; not affiliated with Y Combinator.