Eric Blade

ah, i was under the impression that you were figuring out the area from the quagga box detection, then adding around that. It's an interesting idea that I've been wanting...

I suspect that you are running webpack on an already webpacked module, but I don't know that for sure. It's almost definitely something in your packaging setup, I'd say --...

``` The most important property is `readers` which takes an array of types of barcodes which should be decoded during the session. Possible values are: - code_128_reader (default) - ean_reader...

You can implement any visuals that you want using Quagga's callback input and the canvas. You might look at the onProcessed block here https://github.com/serratus/quaggaJS/blob/master/example/live_w_locator.js

First thing I would do is remove all the irrelevant readers. The more readers you have running, the more problems you will have with different readers potentially making matches, and...

I think so? I use this configuration for reading standard product UPC/EAN/ISBN barcodes: ```` decoder: { readers: ['upc_reader', 'ean_reader'], }, ````

i don't have anything that uses decodeSingle, but I could point to tests.. https://github.com/ericblade/quagga2/blob/master/test/integration/integration.spec.js the tests use a config that looks like ``` return { inputStream: { size: 640 },...

i see you're missing an inputStream, i'm not sure if that's a problem or not, I use the livestream rather than decoding files.

Try a basic config like ```decoder: { readers: ["ean_reader"] },``` get that working first. I can't find any reference to a ean_13_reader or a ean_8_reader, are those something you see...

In general, the VIN decoder works, though like all of the decoders, it's often highly dependent on device and settings. Quagga can be especially touchy to noise around the barcodes...