Mark Keller

> This is the expected behavior but we can investigate whether it can be cleaned up. I will work on making another comment with more details This stems from the...

Thanks for the info and the workaround! It seems the `instanceof` checks are happening within the Arrow source code ([possibly one of these lines](https://github.com/search?q=repo%3Aapache%2Farrow+instanceof+language%3ATypeScript&type=code&l=TypeScript)) and not the DuckDB source code...

Update: we do specify the starlette version in https://github.com/vitessce/vitessce-python/blob/main/pyproject.toml#L66 But perhaps it is not respected when installing other packages at the same time like: ```sh pip install vitessce[all] jupyterlab ```

I think the question comes down to how to create a pyodide package that contains bindings for an existing `.wasm` binary

> I doubt that WASM binaries built with go's build toolchain would be compatible Is this due to a differing ABI between what Emscripten would produce and what the Go...

Ah thanks for reporting this @J-Yash , we probably need to add a parameter to tell the `tifffile` library to use the BigTiff format

Another workaround for now would be to use the tifffile code within those functions directly https://github.com/vitessce/vitessce-python/blob/83b1411f170a96394e6e5e05f5970ca1c0e0dd0c/vitessce/data_utils/ome.py#L41 and manually add the `bigtiff=True` parameter

I think it would be useful to document some general (file format agnostic) solutions if possible, but those that are more specific would be great as well, and the former...

https://github.com/keller-mark/pizzarr/blob/97089fb18b2fe9150f246482e1fb0d88ba70e40b/R/indexing.R#L107

@ilan-gold is passing a `pool` value recommended? I notice we are not doing this in Vitessce - should we be?