Eric Blade

it seems like the best one can do is either use the outdated facing environment constraint in your Quagga init, or filter the enumerate devices to pick one that appears...

fwiw, i was just glancing at the quagga2-redux-middleware package, and realized it's dependency tree was a mess, and released an update just now that hopefully fixes it.

In your constraints, you can specify the deviceId instead of the facing, to get a specific camera device. i think it's actually supposed to be something like ```deviceId: { exact:...

oh, right, i misunderstood. That likely means that your drawing canvas is not positioned over the top of your video element. I get the same situation when I rotate my...

This could really use some cleanup, I've hacked it together from posts on the original repo, as well as my own ideas ```` function getMedian(arr) { const sorted = [...arr].sort((a,...

I think that might be a good feature to actually put into the lib itself, good idea. Barring that, you should be able to either render an element on top...

Honestly, I have not played with the area feature at all, I believe there are some unit tests involving it, so I assume it works. One thing I do know...

fwiw, we may not *need* the blobs, but the existing test framework can't access the worker.js file when it's built using worker-loader. if/when test system gets some significant upgrades, that...

maybe try awaiting Quagga.stop() before calling init again? Also might need to increase that timeout, or maybe do something explicit in Firefox that I'm not aware of to get it...

If you're using the latest point release, you should be able to await Quagga.stop() although that might not necessarily wait until the browser is completely ready to restart the camera