loro-crdt 1.13.1 → 1.13.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 +18 -0
- package/base64/index.js +72 -68
- package/base64/loro_wasm.d.ts +8 -8
- package/browser/index.js +5 -5
- package/browser/loro_wasm.d.ts +8 -8
- package/browser/loro_wasm.js +15 -15
- package/browser/loro_wasm_bg.js +66 -62
- package/browser/loro_wasm_bg.wasm +0 -0
- package/browser/loro_wasm_bg.wasm.d.ts +2 -2
- package/bundler/index.js +5 -5
- package/bundler/loro_wasm.d.ts +8 -8
- package/bundler/loro_wasm_bg.js +66 -62
- package/bundler/loro_wasm_bg.wasm +0 -0
- package/bundler/loro_wasm_bg.wasm.d.ts +2 -2
- package/nodejs/loro_wasm.d.ts +8 -8
- package/nodejs/loro_wasm.js +66 -62
- package/nodejs/loro_wasm_bg.wasm +0 -0
- package/nodejs/loro_wasm_bg.wasm.d.ts +2 -2
- package/package.json +1 -1
- package/web/loro_wasm.d.ts +10 -10
- package/web/loro_wasm.js +65 -61
- package/web/loro_wasm_bg.wasm +0 -0
- package/web/loro_wasm_bg.wasm.d.ts +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,23 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.13.3
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 8d258cb: Fix `unreachable` panic when importing an out-of-order update whose op targets a mergeable child container before its creation (or its parent map) has arrived. Such ops are now buffered as pending and applied once the creating change is imported.
|
|
8
|
+
- 32700ba: Fix undo recording for the first local commit after importing shallow snapshots that need import-time state materialization.
|
|
9
|
+
|
|
10
|
+
## 1.13.2
|
|
11
|
+
|
|
12
|
+
### Patch Changes
|
|
13
|
+
|
|
14
|
+
- 9d7d5c8: Fix `getContainerById` / `hasContainer` for ensured-but-empty mergeable containers.
|
|
15
|
+
After `ensureMergeableMap` (and friends), the child was visible via `map.get(key)`
|
|
16
|
+
and `toJSON()` but its id did not resolve until the first op was written into it —
|
|
17
|
+
locally and on remote peers after sync. The id now resolves as long as the parent
|
|
18
|
+
map's child ref is alive; a mergeable cid that was never ensured still resolves to
|
|
19
|
+
`undefined`.
|
|
20
|
+
|
|
3
21
|
## 1.13.1
|
|
4
22
|
|
|
5
23
|
### Patch Changes
|