zswu

I guess that is why I had decided not to use the bundle js. This issue happend in the old webpack but now webpack seems to work fine. Anyway, seems...

That is great. So we could: * Remove the wasm.bin workaround. * Build a different zbar.js for browser. (Pass arguments to emcc to build only for Web / Worker env)

I know what the bundle is. If you see the readme in v1.0.0, you can find the document about polyfilling `fs` and `path`. But removing them is not that hard...

https://github.com/samsam2310/zbar.wasm/tree/4cc3408006636041e72ec1764866067090a45f3f#how-to-include

This is a workaround for issue [webpack/6725](https://github.com/webpack/webpack/issues/6725)

The warning is because we use `.wasm.bin` for the extension of wasm files. This is a workaround for [webpack/6725](https://github.com/webpack/webpack/issues/6725) because if we use `.wasm` the webpack will try to parse...

Sounds reasonable. We should avoid to use built-in type name.

I'd tested on win10 and linux. But I didn't test on Mac. Base on the error, I guess it could be caused by environment variables.

Hi, It is great that you would like to contribute! Just fork the project and you can create PR from your forked repo. Here is the [official document](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork). Also I'm...

Since the message is `ERROR: No loader is configured `, maybe you just need to config a loader for `*.wasm.bin` ?