-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edge support? #19
Comments
I think I tried it and it works, but I may be wrong. It doesn't use fs if it's not available. |
Oh great okay will try! |
let me know how it goes |
mmm it did not work (at least on vercel) but I dont remember why. Will update this thread when I retry it. |
It doesn't seem to be working for me due to the (node)
|
Strange, it should only import 'https' if 'fetch' isn't available. Conditional imports are a lie. |
In cloudflare workers (and I presume Vercel as well, as they use the cloudflare runtime under the hood) you need to setup a binding to a WASM binary and then reference it. See https://developers.cloudflare.com/workers/platform/web-assembly/javascript/ So without some bundler magic to replace the WASM import in the lighter code, I don't think it'll work right now. |
I had problems with old versions of Next.js (they were ignoring the |
I think right now this wont support edge based on how it is loading the WASM (and due to dependence on FS although maybe the browser version can be used?). I wondered if somehow using https://vercel.com/docs/concepts/functions/edge-functions/wasm this could be shipped to an edge function, though.
The text was updated successfully, but these errors were encountered: