Erik Hermansen

Re #1, I know "better documentation" is on the TODO list. But I will tell you how I usually figure it out: * https://github.com/ccoreilly/vosk-browser/blob/master/src/bindings.cc - shows the methods on Recognizer...

To be clear, I'm not the maintainer. Just another user like you. But it occurs to me that converting number text to numbers is possible, useful to me as well...

Just making a quick guess from vague memories of handling the same/similar issue... I think maybe it's something related to a newer version of WebPack causing `process` to be undefined....

I think I agree it would be nice to have, and maybe that feature is already there and I missed it. But... If you maintain your own ready state and...

It's a little too much for me to find the issue in that code. I'll say that I would suspect that the setter functions (e.g. `setRecognizer()`, `setLoading()`) might not be...

I don't trust my eyes and mind to sort out the React-based state logic above. That's why I say it might be useful for you to narrow down the issue...

> Do you know how to stop the recognizer from "recognizing"? One way is to stop sending samples to the recognizer via .acceptWaveform(). So in your audioworklet, you can check...

I think there are a few more missing transitive dependencies too. My offer is to write a PR that makes them implicit so that a consuming Typescript/type-checked project need only...

Also, I am happy to help with more information, troubleshooting, even drafting a little text for your docs, if you like. Publii is great software, and I love open source.

I've resolved the problem for myself, and wrote a doc here describing in some detail how to avoid the problem and fix it if you have it - https://decentapps.net/info/using-publii-with-github-actions.html Publii...