Bedis Nbiba
Bedis Nbiba
Still the same issue, can't run the browsers with manual explore - system fedora 40 - browser tested - chrome flatpak, chrome native, firefox native
```ts import { encodeBase64 } from "jsr:@std/encoding/base64"; encodeBase64(Deno.readFileSync(Deno.execPath())); ``` this crashes with out of memory error, if I use node buffer insteada it finish in a couple of milliseconds
What about running the node code if we're on a server context and the current version (or an optimized one) if we detect we're on the browser
Also is it ok for std to use wasm libraries, in that case even the browser branch can be made efficient
Presonally I think you should just use wasm for this , it's the best use case of wasm (pure math work), I imagine it's going to be faster then any...
Here is a benchmark  ```ts import { decodeBase64 as decodeBase64Wasm, encodeBase64 as encodeBase64Wasm, } from "jsr:@sigma/rust-base64"; import { decodeBase64 as decodeBase64Std, encodeBase64 as encodeBase64Std, } from "jsr:@std/encoding"; import {...
I'm not sure it feels weird to me that an assert equal doesn't work after a certain size, also the error is not helpful
The use case is for Deno so I don't have to give network permission when the json files are part of the import graph
With the other benefits that it can be vendored or even embedded into Deno compiled app
Thanks >Is speed important for you ? Personally for this package, not that much