Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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] https://fetchable.org/ [2] https://answers.netlify.com/t/support-fetch-for-netlify-edge... [3] https://server-js.com/



Ivan from Netlify here, we should do it! our most recent release for Functions added support for Fetchable (https://docs.netlify.com/build/functions/overview/#web-reque...), we should do this for Edge Functions as well.


Thanks! Really hoping to see this working, I already support Functions thanks to this, would love to support Edge Functions as well through Fetchable :)


That's weird, considering the guy who put the fetchable.org website up works at Netlify.


That's so funny and ironic, I missed that little detail! Hey, this might be a way for adding internal pressure if he's the only one asking for it.


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




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: