Trevor Manz

We've also experienced this issue in https://github.com/hms-dbmi/vizarr as suggested here: https://github.com/danmarshall/deckgl-typings/issues/126, I think explicitly declaring the types in your project fixes the issue (but I'm not sure why): ```javascript //...

This only seemed to be an issue when I tried to generate a single bundle for the corresponding worker. However, marking `threads/worker` as `external` works just fine. It seems the...

Thanks for pinging me @rabernat. Hoping I can share lessons learned from zarr.js & Viv.

Microscopy community has started to unify around standard / convention: - https://ngff.openmicroscopy.org/latest/#multiscale-md - https://forum.image.sc/t/multiscale-arrays-v0-1/37930 (think @joshmoore will be talking about this at Dask Summit?) Some sample datasets from the Image...

I absolutely love the idea of dynamic re-chunking, and it's something I've been experimenting with myself. It's also easy to imagine swapping compression on the server, e.g. from lossless to...

> Agreed. Doesn't seem like a difficult requirement; don't see why a `ZarrLoader` would even need to know if the Zarr dataset is static or dynamic. Totally agree. I've just...

> I wonder, does Vite not like the template approach? Yeah this is the primary "issue". Vite out of the box assumes 1:1 mapping of files on disk to your...

Hmm really odd error in the CI. I tried to track I down earlier to no avail..

Just want to put own my current observations here and list things that I think should be discussed/investigated. Both `zarr.js` and `geotiff.js` use `pako` for decoding arrays encoded via `Zlib`....

hmm I'm getting the same error as CI. Try a fresh install. `rm -rf node_modules && pnpm clean` then `pnpm install`.