Release 0.22.0: localStorage engine, Tauri bridge, npm package rewrite

[Tam1SH]

0.22.0

Breaking

• Store::subscribe returns a StoreSubscription that unsubscribes when dropped, in place of a bare id.
• SubscriptionId is a type of its own, drawn from one count per process: an id from one store names nothing in another. StoreBackend::unsubscribe returns whether this store held it.
• MemoryStore::open(&config, migrations) takes the steps and returns (store, report): a store opened on the memory engine by name runs its steps like any other.
• Source gains AnotherPage, and StoreEvent::is_external_edit is true for it.
• gpui adapter 0.3.0: AmeView<T> and AmeEntity<T> lose the store parameter; new_amethystate panics when the slice will not open, try_new_amethystate returns the error. Built on gpui-pre 0.3.6, Rust 1.95.
• npm amethystate 0.4.0 is rewritten: Field, ReactiveMap, load() into a slice, a Transport with tauri() as the default. get() is synchronous and subscribe returns its unsubscribe, the useSyncExternalStore and Svelte store contract.
• amethystate-codegen writes strict TypeScript classes over that package; value types come from ts-rs, derived only where the frontend sees them.
• amethystate-reactor is removed.

New

• Backend::LocalStorage (feature localstorage), for a page on wasm32-unknown-unknown: one JSON value per key, a write in the call, a full quota answered by set, another tab's write arriving as Source::AnotherPage. StoreLayout::PageStorage { under } says where it lives.
• Async twins for what waits on the disk: StoreBackend::save_async and close_async, shutdown_async, GlobalStoreGuard::close_async.
• The memory engine reads in parallel, as redb does.
• The Tauri plugin has delete_prefix and scan_keys, both in amethystate:default.
• The yew adapter works without Tauri: AmeStateProvider, use_field, use_read_only_field, use_map, use_map_entry, use_amethystate over a local store.
• cargo xtask browser runs the whole test suite in headless Chrome.

Fixes

• Tauri frontends hear events again: the listener goes through the Tauri 2 event plugin.
• A path stays watched while anyone still watches it; the first unsubscribe ended it for everybody.
• Deleting a prefix that covers a watched map clears the map on the frontend.
• A map write from a Rust frontend applies at once and rolls back when refused: an entry no longer flashes as removed while its write is in flight, and a new one no longer vanishes right after it is added.
• The leptos and dioxus Tauri paths build again.
• A text store closing on Windows while its directory changed could hang the file watcher and whichever thread next opened a file there; notify moves to 9.0.0-rc.5, which stops a watch without that race.
• cargo xtask browser removes the Chrome profile each run leaves, about 30 MB apiece.

Also here

• Every example is the same multi-page todo app; new web-dioxus and web-yew, and tauri-typescript in place of tauri-settings.
• The book: a TypeScript page for the new package, a browser section on the installation page, corrected Tauri and gpui pages.
• CI type-checks and tests the npm package.

Warning

The framework adapters and about half of the engines are not used in any real application. They run in CI and were smoke-tested, and they were built as a proof of concept for the architecture of the store.

🤖 Generated with Claude Code