Add support for 7 compression plugins

[axelboc]

Took me a while to figure out how to fetch the plugin files from the webview, but I got there in the end. Unfortunately, I'm hitting the following issue with some of the larger plugins (LZ4, ZStandard, etc.):

hdf5_util.js:8 RangeError: WebAssembly.Compile is disallowed on the main thread, if the buffer size is larger than 4KB.
Use WebAssembly.compile, or compile on a worker thread.

The webview fetches the plugin files correctly, and they get written to the Emscripten file system as expected. The problem seems to occur when h5wasm reads the compressed dataset and HDF5 tries to load the appropriate plugin dynamically.

@bmaranville I assume there's no other workaround than to move @h5web/h5wasm to a worker, right?

[bmaranville]

This was a limitation of Chrome and Chrome-based browsers (including headless, I'm sure) until recently. The limitation was removed months ago (just before the HDF5 User Group meeting - I talked about it there). Simplest solution is just to upgrade to a more recent browser version. The issue doesn't seem to affect other engines (like those in Safari or Firefox)

[axelboc]

Right, hmm this sucks then, because I'm on the latest version of VS Code... Maybe VS Code or Electron enforces this limitation internally on purpose to avoid blocking the main thread. 🤔

[bmaranville]

I'm guessing it means they're still on a slightly older JS engine - eventually the problem will go away (maybe?)

[bmaranville]

If you are going to move it to a worker, it seems like you could reuse the h5grove api definitions and write a worker that provides those endpoints. I don't imagine that would be too much work, and could be useful in the browser too.

[bmaranville]

Have you looked into preloading the plugins, as described here? https://emscripten.org/docs/porting/files/packaging_files.html#preloading-files

[axelboc]

Well... seems that patience pays! 😂 With the upgrade to Electron 27 in VS Code 1.86.0, the error is gone and the plugins load successfully. 🎉

I'll keep the goal of moving to a worker on the back burner, as this is still the better approach in the long term.