Netlify Edge Functions lack support for Fetchable standard
Problem
Users want to use the Fetchable standard in Netlify Edge Functions to write portable code across runtimes. Lack of support forces library authors to maintain runtime‑specific workarounds, increasing maintenance overhead.
Pain points
- Need a unified cross-runtime Fetch API
- Having to write and maintain workaround code for Netlify Edge Functions
- Hinders library authors from writing portable npm packages
Questions to verify
- Will Netlify consider adding Fetchable support in its roadmap?
- When can users expect cross‑runtime Fetch standard support?
- Are there alternative standards being considered?
Evidence
quote · @Anonymous
If someone in Netlify is listening, could you please add support for Fetchable in Netlify Edge Functions? I opened a ticket 1 week ago but it has gone unanswered. 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")}!`) } }`
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.