chore(deps): bump zarrita from 0.6.1 to 0.7.2

[dependabot]

Bumps zarrita from 0.6.1 to 0.7.2.

Release notes

Sourced from zarrita's releases.

zarrita@0.7.2

Patch Changes

• Fix UnknownCodecError when reading zarr v2 arrays that use the bitround or json2 codec. (#416)

zarrita@0.7.1

Patch Changes

• Drop FileSystemStore from the zarrita root barrel, which accidentally landed in 0.7.0 as part of #384. Node users who still want FileSystemStore can import it directly: (#411)

  import { FileSystemStore } from "@zarrita/storage";
  // or
  import FileSystemStore from "@zarrita/storage/fs";

• Fix TypeError: Do not know how to serialize a BigInt when opening an int64/uint64 array from a withConsolidatedMetadata store. (861b5fb)

zarrita@0.7.0

zarrita aims to be a delightful little library for working with Zarr in TypeScript. Since the v0.5 rewrite, its abstractions had started forcing users past the public API to get real work done (#349, #310, #325, #352). v0.7 addresses that on two fronts: extensibility and correctness.

Most real use cases weren't about writing new stores — they were about layering behavior over an existing store: caching, request batching, auth, virtual-format translation. People were doing that through subclassing and hand-rolled proxies. v0.7 makes layering a first-class operation. The other gaps were places where the library silently returned wrong answers on real data.

[!NOTE] This release deliberately contains (minimal) backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of zarrita in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ~0.6.0. See npm's documentation about semver for more information.

To upgrade, please see the migration guide.

Extensions

Before v0.7, zarrita had extension points for custom codecs and custom stores (implementing AsyncReadable from scratch), but nothing for layering behavior on an existing store. Adding features to a FetchStore meant subclassing it, wrapping it in a hand-rolled Proxy, or smuggling per-call state through the AsyncReadable<Options> generic. Intercepting at the chunk layer meant replacing zarr.Array with a bare Proxy entirely; there was no extension point there at all.

v0.7 introduces two extension points, one per layer:

Layer	Intercepts	Primitive	Composer
Transport	store.get(key, range)	zarr.defineStoreExtension	zarr.extendStore
Data	array.getChunk(coords)	zarr.defineArrayExtension	zarr.extendArray

Store extensions handle paths and bytes. Array extensions handle chunk coordinates. A factory receives the inner value and user options and returns method overrides; everything else is delegated through a Proxy. Compose extensions in a pipeline:

let store = await zarr.extendStore(
  new zarr.FetchStore("https://example.com/data.zarr"),
  zarr.withConsolidatedMetadata,
  (s) => zarr.withRangeCoalescing(s, { coalesceSize: 32_768 }),
  (s) => zarr.withByteCaching(s),
);
let arr = await zarr.open(store, { kind: "array" });
</tr></table>

... (truncated)

Commits

• 4a2feb5 Version Packages (#417)
• a5049b1 Correct several mistakes in docs (#414)
• 28d884b Register numcodecs.bitround and numcodecs.json2 for v2 reads (#416)
• 8c1b160 Version Packages (#412)
• 861b5fb Fix BigInt cache corruption in consolidated v3 (#413)
• 7047960 Drop FileSystemStore from the zarrita root barrel (#411)
• 47b3091 Version Packages (#360)
• 7f03182 Edit release notes and docs (#408)
• 6b25b93 Draft v0.7.0 release notes (#407)
• 5ef863c Set --no-check for deno publish (#406)
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
zarrita	[< 0.5, > 0.4.0-next.14]