> Development branch documentation · commit 327c05c78d2f528e4f4a679fcc7a77d9aa161f48
> Package versions: @zenfg/webgpu 0.1.0, @zenfg/snapshot 0.1.0, @zenfg/inspector 0.1.0, zenfg 0.1.0, zenfg-snapshot 0.1.0
> Source: https://github.com/uinosoft/zenfg/blob/327c05c78d2f528e4f4a679fcc7a77d9aa161f48/docs/compatibility.md

# Compatibility matrix

<!-- generated:compatibility:start -->
| ZenFG package | Version | Runtime/toolchain | Snapshot |
| --- | --- | --- | --- |
| `@zenfg/webgpu` | `0.1.0` | Native WebGPU; tooling Node >=24.0.0 <25 | produces 1.2 |
| `@zenfg/snapshot` | `0.1.0` | ESM, ES2022 | reads Legacy V0, Legacy Candidate V1, 1.1 (migrated), 1.2 |
| `@zenfg/inspector` | `0.1.0` | Modern DOM; no WebGPU dependency | reads through @zenfg/snapshot |
| `zenfg` | `0.1.0` | Rust 1.98; wgpu 30.0.1 | produces 1.2 |
| `zenfg-snapshot` | `0.1.0` | Rust 1.98; no wgpu | reads Legacy V0, Legacy Candidate V1, 1.1 (migrated), 1.2 |
<!-- generated:compatibility:end -->

Package versions do not lockstep. A Snapshot major/minor change requires an
explicit reader migration; unknown formats and versions are rejected.

Released beta.2 used Snapshot 1.0; released beta.3 used Snapshot 1.1. Beta.4
produces 1.2 and explicitly migrates 1.1; canonical 1.0 remains rejected.
Readers must be upgraded before opening newly produced 1.2 files. See the
[beta.3 migration guide](/zenfg/docs/migration/beta-3.md) for archived captures and
source-level API changes.

Version 0.1.0 preserves the beta.4 public APIs and Snapshot 1.2 format. Public
APIs may change before 1.0; integration projects should pin exact package
versions and review migration notes before upgrading.

## Repository toolchains

<!-- generated:toolchains:start -->
Repository tooling: Node `>=24.0.0 <25`, npm `>=11.11.0 <12`, TypeScript `^6.0.3`, Rust `1.98`, wgpu `30.0.1`.
<!-- generated:toolchains:end --> Node.js is required for development and packaging, not for browser
runtime use. Browser execution depends on native WebGPU and modern DOM support.

TypeScript consumers should import documented package entrypoints rather than
source files or undeclared `dist` paths. Rust consumers should use the feature
flags documented by each crate. Toolchain changes are validated by the release
checks before package publication.

See [Unified timing and Snapshot 1.2 migration](/zenfg/docs/migration/timing-snapshot-1-2.md) for the beta.4 API changes.