@laboverwire/stitch 0.6.1 → 0.6.3
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 +16 -0
- package/package.json +10 -8
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,22 @@
|
|
|
6
6
|
|
|
7
7
|
- _Nothing yet._
|
|
8
8
|
|
|
9
|
+
## 0.6.3
|
|
10
|
+
|
|
11
|
+
### Fixed
|
|
12
|
+
|
|
13
|
+
- **Resolved the `time not implemented on this platform` wasm panic** that fired on the first child `create()` in the browser and then failed every subsequent store call. The bug was in `stitch-rs` (fixed in stitch-rs #44) and shipped as `@laboverwire/stitch-wasm` 0.5.1; this release delivers it to consumers by raising the floor below. This is the panic the 0.6.2 entry noted as **not yet fixed** and tracked against MQDB.
|
|
14
|
+
|
|
15
|
+
### Changed
|
|
16
|
+
|
|
17
|
+
- Raised the `@laboverwire/stitch-wasm` floor to `^0.5.1`. `^0.5.0` already resolves 0.5.1 on a fresh install, but raising the floor guarantees the fix above is present rather than leaving it to resolution order. 0.5.1 is API-identical to 0.5.0, so there are no `@laboverwire/stitch` type or signature changes. The 0.4 → 0.5 engine change that switched failed `Store` methods from rejecting with a plain string to a structured `Error` (`message` + `kind`) does not affect this wrapper: the adapter forwards rejections untouched and never matches on error strings, so callers receive whatever shape the engine emits.
|
|
18
|
+
|
|
19
|
+
## 0.6.2
|
|
20
|
+
|
|
21
|
+
### Changed
|
|
22
|
+
|
|
23
|
+
- Raised the `@laboverwire/stitch-wasm` floor to `^0.5.0`. The engine's 0.4 → 0.5 is a breaking minor, but the wrapper's binding contract is unchanged — identical wasm type surface and identical public bindings — so there are no `@laboverwire/stitch` type or signature changes. This is a currency bump: `^0.4.0` cannot resolve `stitch-wasm@0.5.0` (a 0.x minor is a breaking bump), which left consumers pinned below the latest engine. It is **not** a fix — it does not resolve the `time not implemented on this platform` wasm panic (tracked separately against MQDB).
|
|
24
|
+
|
|
9
25
|
## 0.6.1
|
|
10
26
|
|
|
11
27
|
### Fixed
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@laboverwire/stitch",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.3",
|
|
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.
|
|
77
|
+
"@laboverwire/stitch-wasm": "^0.5.1"
|
|
78
78
|
},
|
|
79
79
|
"peerDependencies": {
|
|
80
80
|
"react": "^19.0.0",
|
|
@@ -92,9 +92,9 @@
|
|
|
92
92
|
"@eslint/js": "^10.0.1",
|
|
93
93
|
"@testing-library/react": "^16.3.2",
|
|
94
94
|
"@types/react": "^19.2.18",
|
|
95
|
-
"@vitest/browser": "^4.1.
|
|
96
|
-
"@vitest/browser-playwright": "^4.1.
|
|
97
|
-
"@vitest/ui": "^4.1.
|
|
95
|
+
"@vitest/browser": "^4.1.11",
|
|
96
|
+
"@vitest/browser-playwright": "^4.1.11",
|
|
97
|
+
"@vitest/ui": "^4.1.11",
|
|
98
98
|
"esbuild": "^0.28.1",
|
|
99
99
|
"eslint": "^10.8.0",
|
|
100
100
|
"eslint-config-prettier": "^10.1.8",
|
|
@@ -111,10 +111,12 @@
|
|
|
111
111
|
"typescript-eslint": "^8.66.0",
|
|
112
112
|
"vite-plugin-top-level-await": "^1.6.0",
|
|
113
113
|
"vite-plugin-wasm": "^3.6.0",
|
|
114
|
-
"vitest": "^4.1.
|
|
115
|
-
"vue": "^3.5.
|
|
114
|
+
"vitest": "^4.1.11",
|
|
115
|
+
"vue": "^3.5.42"
|
|
116
116
|
},
|
|
117
117
|
"overrides": {
|
|
118
|
-
"uuid": "^11.1.1"
|
|
118
|
+
"uuid": "^11.1.1",
|
|
119
|
+
"brace-expansion": "^5.0.12",
|
|
120
|
+
"source-map-js": "^1.2.2"
|
|
119
121
|
}
|
|
120
122
|
}
|