Dario Piotrowicz

Hi @lcswillems 👋 Thanks for the issue 🙂, unfortunately I think that supporting the Node.js runtime is quite out of the question, mainly for two reasons: - This adapter works...

@lcswillems as I mentioned above: ``` This adapter works by generating a worker using the Vercel CLI build command (vercel build) output, such output comprises of edge functions and (AWS)...

This is blocked by: https://github.com/cloudflare/next-on-pages/issues/623 (and https://github.com/cloudflare/next-on-pages/pull/648) since `node-fetch` is being used in the `setupDevBindings` utility, so we first need to update such utility (which can also remove the `node-fetch`...

### Note This issue is blocked by: https://github.com/cloudflare/next-on-pages/issues/202 and https://github.com/cloudflare/pages-plugins/issues/30 Most likely solving the two issues above should in turn also solve this one

No problem, sorry this is taking so long :sweat:, I'll definitely look into #202 soon (likely this or next week), I'll try to also get the pages-plugins one solved soon-ish...

#202 has been resolved, so now it should just be the pages-plugin one that needs addressing 🙂

Sorry I misunderstood things, we don't necessarily want to force developers to use the vercel-og pages plugin, so that is not blocking this `@vercel/og` anyways isn't yet currently working on...

Hi @lucaswalter, no I'm sorry, I had a quick look some time ago but haven't dug much into it since, so it's still unresolved 😓

@lucaswalter as far I know there actually isn't a real blocker, it's just a matter of finding the time to dig into what the issue with `vercel/og` actually is. it's...

No problem @lucaswalter 🙂 Check out #325 we're very close! 😄 (feel free to try out the [next-on-pages prerelease](https://github.com/cloudflare/next-on-pages/pull/325#issuecomment-1604457773) and let me know if it works for you if you...