You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the compiled wasm code is loaded dynamically with an encoded string in lib.js. I believe you can replace that file and the init step in canvaskit.ts with a plain import if you are comfortable releasing a new version that is only compatible with deno 2.1+. I am mainly going off the information I see in this deno blogpost https://deno.com/blog/v2.1. It is possible that there is something more complicated about this module that will prevent this. At the very least though, it should remove an async init stage to canvas usage, which should help simplify usage.
The text was updated successfully, but these errors were encountered:
That would be interesting, I believe it would be more complicated than that due to how canvaskit loads the wasm. If there was a way to import as a WebAssembly Module, not an instance, that would make it easier to integrate but this requires quite a bit of rewiring
Currently the compiled wasm code is loaded dynamically with an encoded string in lib.js. I believe you can replace that file and the init step in canvaskit.ts with a plain import if you are comfortable releasing a new version that is only compatible with deno 2.1+. I am mainly going off the information I see in this deno blogpost https://deno.com/blog/v2.1. It is possible that there is something more complicated about this module that will prevent this. At the very least though, it should remove an async init stage to canvas usage, which should help simplify usage.
The text was updated successfully, but these errors were encountered: