BinBashBanana

Most browsers disable XHR/fetch to `file://` urls, for security reasons. You could theoretically embed the .wasm file into the .js file and it could work. Or see [here](https://emscripten.org/docs/getting_started/FAQ.html?highlight=single_file#how-do-i-run-a-local-webserver-for-testing-why-does-my-program-stall-in-downloading-or-preparing). > When...

(Doing this may increase load times, because modern WASM streaming won't work)

This is why I want to use a service worker cache, it will make it much easier for the asset bundle, cores, and BIOSes. > In v6.6 I plan to...

Although, now that I think about it, service workers may not work on `file://` urls either. I'll check.

[MDN](https://developer.mozilla.org/en-US/docs/Web/API/Cache) Says: > Note that the `Cache` interface is exposed to windowed scopes as well as workers. You don't have to use it in conjunction with service workers, even though...

Just a heads up, this is not dynamic linking. Dynamic linking is something else I have planned for the future, see [here](https://emscripten.org/docs/compiling/Dynamic-Linking.html).

I think automatically downloading everything would be a bad idea, so I want to have a manager (one of the modal windows) for it. Unobtrusive would probably be best (?)

Something like that yeah. There are no per-core assets, besides the BIOS files. So it could look like: - Asset bundle - Core: Beetle PSX HW - BIOS: Beetle PSX...

It's all good. I frequently feel demotivated as well.

> Is it possible to load them from the web server it's hosted on? Yes, but this won't be the case for the demo (github.io) > the same zip file...