Mark Keller

Behavior should be the same between all stores (e.g., MemoryStore and DirectoryStore) - currently I think it is not as `file.exists` will return TRUE for a directory. Also, behavior should...

> Wondering what your preferred implementation is My first thought would be to add an optional property to the Store abstract class for keeping consolidated metadata at the store-level. If...

Haha, happy Monday! Thanks for sharing the implementation. > How do you feel about use of memoise as I have in there? It makes sense, especially for HTTP store! I...

Ah I see now the empty object is an iterator so I can do ```js Array.from((await zarr.get(arr)).data); ``` so perhaps not a bug after all, but now I have to...

Maybe the user should opt-in to getting an iterator `zarr.getIterator(arr)`

It might be helpful to think of this less like a memory leak and more of an issue of documenting / clarifying the widget lifecycle. A basic counter example demonstrates...

> We should load ESM once, upfront for the widget class It might need to involve some kind of string hashing to ensure that widget development can still occur directly...

Is there a reason this cannot be resolved by reusing the same widget instance on the Python side?

Part of what I proposed is to store x- and y-coordinates of points relative to the edge of the Zarr chunk -- as opposed to "absolute" (i.e., relative to the...

It was intentional not to export the class, and instead export the utility functions that use the class internally