@laboverwire/stitch 0.7.0 → 0.7.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +10 -0
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,16 @@
|
|
|
4
4
|
|
|
5
5
|
- _Nothing yet._
|
|
6
6
|
|
|
7
|
+
## 0.7.1
|
|
8
|
+
|
|
9
|
+
### Fixed
|
|
10
|
+
|
|
11
|
+
- **A scope opened by a second viewer no longer comes up empty on a cold load.** A viewer that opened a scope it did not create — via `replaceScope` while the transport was already `connected` — received the scope's children only intermittently (roughly 40% of cold opens stayed empty until a full page reload). The root cause was engine-side and wasm-specific: `replace_scope`'s server-open branch, which fetches the scope's root and children from the broker, was compiled out on `wasm32`, so a connected `replaceScope` in the browser only read local persistence — empty for a viewer with nothing cached — while the sole wasm server-open path (backfill-on-connect, added in 0.6.1) raced the open and usually no-opped. Fixed in the engine (stitch-rs#92, closing stitch-rs#91) and shipped as `@laboverwire/stitch-wasm` 0.6.2: the connected server-open branch now runs on all targets, so a connected `replaceScope` reconciles the scope's root and children itself and the scoped read hooks (`useScopedEntities`, `useEntitySnapshot`, and their Vue equivalents) converge with no reload. Regression-tested upstream (`connected_replace_scope_delivers_children_to_a_second_viewer`, native broker, plus a broker-gated wasm test); this repo adds no wrapper test, as the path cannot be exercised without a live broker. This supersedes the partial 0.6.1 improvement (stitch-rs#85) and resolves the empty-scope symptom tracked in this repo as #67; the React `useSyncScope` latch was ruled out as the cause and is unchanged.
|
|
12
|
+
|
|
13
|
+
### Changed
|
|
14
|
+
|
|
15
|
+
- Raised the `@laboverwire/stitch-wasm` floor to `^0.6.2`, which delivers the connected-open fix above. 0.6.2 is a patch over 0.6.0/0.6.1 and additive to the `Store` surface this adapter consumes, so there are no `@laboverwire/stitch` type or signature changes.
|
|
16
|
+
|
|
7
17
|
## 0.7.0
|
|
8
18
|
|
|
9
19
|
### Changed
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@laboverwire/stitch",
|
|
3
|
-
"version": "0.7.
|
|
3
|
+
"version": "0.7.1",
|
|
4
4
|
"description": "Reactive state synchronization library bridging an in-memory store, IndexedDB persistence, and MQTT-based remote sync.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"author": "LabOverWire",
|
|
@@ -74,7 +74,7 @@
|
|
|
74
74
|
}
|
|
75
75
|
},
|
|
76
76
|
"dependencies": {
|
|
77
|
-
"@laboverwire/stitch-wasm": "^0.6.
|
|
77
|
+
"@laboverwire/stitch-wasm": "^0.6.2"
|
|
78
78
|
},
|
|
79
79
|
"peerDependencies": {
|
|
80
80
|
"react": "^19.0.0",
|