-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Cairo WebAssembly Build Target & Deno Support #1653
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
Comments
I know this may mean a reduction in performance, but the portability would be vastly improved and being able to support node environments without build tooling would be a huge benefit. Aside, came across this, because I had been wanting to create a github repo that would separately publish the wasm modules from the squoosh project in more easy to use wrappers for use in browser, node and deno. |
It's definitely a good idea. I'm eager to see benchmarks. To keep the convo in one place, mind if I close this and continue in #1652? |
@zbjornson don't mind at all.. just didn't necessarily want to muddle, and definitely think Deno as an optional target should be part of the conversation. |
Any idea when we would be able to use this from deno? |
👍 for wasm. It would be easier to install and use anywhere then... |
With Edge functions in Netlify, Vercel, etc, this should be moved to priority. J |
Given that recent versions of Node support WebAssembly, it might be a good idea to create a Cairo build target for wasm, so that it can be included directly in the module without the requirement of a separate Binary download.
Second to this would be the ability to more easily support a Deno build target for deno.land
There's been some discussion and work towards being able to accomplish this in #1258 and #1652
The text was updated successfully, but these errors were encountered: