-
Notifications
You must be signed in to change notification settings - Fork 55
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
Wasm / frontend support #84
Comments
There is a WASM build, but you have to build from source as it isn't published to eg.
You can also build for WASI and run with eg. wasmtime. See Line 46 in fe6de19
To manage expectations, I will warn you that the WASM build is currently much slower than the native build. This is for two reasons:
|
Okay I've got it working now, I'm not too worried about speed and I'm getting far more useful results than I was getting for tesseract.js so I'm pretty happy. |
Yes, I think so. There isn't an existing tracking issue for publishing an npm package. |
I'm trying to implement this in the browser but I keep getting an error Steps I took:
Implementation:
The length log statements match the size of the models on disk. |
Hello @hbmartin, this library reads models in |
I see that there is a nodejs example in the repo but is it possible to use this on the frontend yet with ts support?
The text was updated successfully, but these errors were encountered: