Sam Clegg

I think this can be closed now? Or is there more to do?

Indeed it looks like we should loading the preload data file relative to the `.mjs` files by default. BTW, have you considered switching from `--preload-file` to `--embind-file` the later will...

https://emscripten.org/docs/porting/files/packaging_files.html#packaging-using-emcc

Is `worker = new Worker(new URL("my.js", import.meta.url), workerOptions)` a problem on its own? Of is it only when doing nested bundling? i.e. is webpack re-writing this line to be something...

If you do `new Worker(Module["wasmJsURL"].href, workerOptions);` then won't it be impossible for webpack to see the name of the file you are trying to load and therefore make it impossible...

Right, I guess when you do `worker = new Worker(new URL(my_js, import.meta.url), workerOptions);` then webpack doesn't know what file you are trying to load so it can't actually bundle said...

I've added some basic testing of threads with webpack rollup and vite (#23753). I think we still lack coverage of your specific case here, but we are making progress.

Most likely if you use Qt you probably want to let it handle all the interaction with he mouse etc. Trying to do you own mouse interaction underneath Qt will...

I see.. they you need to handle the event directly so that you can request the pointer lock. In that case yes you probably do need to register your own...

My guess is that its an emscripten issue, but I'm not sure how this API is supposed to work TBH. Needs more investigation.