Support for edge runtimes like cloudflare workers, vercel edge, deno etc

[cosbgn]

As a feature request, it would be amazing if this library could work on cloudflare workers, deno, vercel-edge, netlify-edge and other edge runtimes.

These runtimes are gaining a lot of popularity lately, but unfortunately can't be used with this library. I guess this is also due to dependancies like ajv, but there are some edge ready alternatives like @cfworker/json-schema.

Thanks for considering it.

[erunion]

I would love to support Edge runtimes! Do you have a solid way of detecting a package that doesn't support it?

[cosbgn]

Not really, I think the easiest is just to use wrangler dev locally and see if an error comes up.

So far I've learned that:

• Imports needs to be prefixed (e.g. import { Buffer } from 'node:buffer')
• The nodejs_compat flag helps a lot, can easily be activated on cloudflare and active by default on vercel-edge
• ajv doesn't work, but @cfworker/json-schema does
• eval(), new Function(), setTimeout([string]), and setInterval([string]) can't be used.

[erunion]

Do you have an example code snippet for oas that's not working with wrangler dev? Would be helpful to see and debug. I know we only use ajv in oas/reducer, which isn't exported from any main export, and only really exists in this repository because it's used in https://github.com/readmeio/rdme

[cosbgn]

This is the started wrangler which fails on npm run start: https://github.com/cosbgn/oas-edge

[erunion]

Ah gotcha, so its failing on oas-normalize likely then. Moving that off ajv is going to be a lot of work because we'll have to move @readme/openapi-parser and then rewrite @readme/better-ajv-errors as well. 😓

[cosbgn]

oas-normalize would be great as well, but it's failing also without it, only with oas check the new commit without normalize: https://github.com/cosbgn/oas-edge/blob/main/src/index.js

[erunion]

Woof, ok I see now.

[kanadgupta]

@cosbgn I know it's been a while, but a few things have changed so I think we might be in good shape now:

• We recently overhauled our parsing packages so I believe all of our URL resolvers in json-schema-ref-parser are backed by fetch
• All of the runtimes in question (i.e., Cloudflare, Vercel, and Deno, the latter of which powers Netlify's edge runtime) have pretty solid compatibility with most (if not all?) of the Node APIs we need

Are you still blocked on this?

[cosbgn]

Hey @kanadgupta I moved to a different setup because it was incompatible so I'm not using or blocked by this.

This said it's great if you get it to work on the edge, I might revisit it again soon.