chore: fix code examples and make tests pass

Author: zxch3n

deno.lock

@@ -1,4 +1,4 @@
-import { LoroDoc } from "npm:loro-crdt@1.0.0-beta.5";
+import { LoroDoc } from "npm:loro-crdt@1.5.2";
 
 const doc = new LoroDoc();
 doc.getCursorPos;

deno_scripts/loro.ts

@@ -2,7 +2,7 @@ import { walk } from "jsr:@std/fs";
 import { CodeBlock, extractCodeBlocks } from "./extract_code_blocks.ts";
 import { resolve } from "https://deno.land/[email protected]/path/mod.ts";
 
-const LORO_VERSION = "1.2.5";
+const LORO_VERSION = "1.5.2";
 
 async function* scanMarkdownFiles(dir: string): AsyncGenerator<CodeBlock[]> {
   // Walking through the directory to find markdown files
@@ -71,7 +71,7 @@ for await (const blocks of scanMarkdownFiles(targetDir)) {
     }
     await Deno.stdout.write(
       new TextEncoder().encode(
-          `\r🧪 ${testCases} tests, ✅ ${passed} passed, ❌ ${failed} failed`,
+        `\r🧪 ${testCases} tests, ✅ ${passed} passed, ❌ ${failed} failed`,
       ),
     );
   }));

deno_scripts/run_code_blocks.ts

@@ -25,7 +25,7 @@ expect(doc.getChangeAt({ peer: "0", counter: 0 }).message).toBe("test");
 
 Advanced Example - Creating a Merkle DAG:
 
-```ts
+```ts no_run
 const doc = new LoroDoc();
 doc.setPeerId(0);
 doc.subscribePreCommit((e) => {
@@ -73,7 +73,7 @@ EphemeralStore is a better alternative to Awareness for ephemeral states:
 
 Awareness is commonly used as a state-based CRDT for handling ephemeral states in real-time collaboration scenarios, such as cursor positions and application component highlights. As application complexity grows, Awareness may be set in multiple places, from cursor positions to user presence. However, the current version of Awareness doesn't support partial state updates, which means even minor mouse movements require synchronizing the entire Awareness state.
 
-```ts
+```ts no_run
 awareness.setLocalState({
   ...awareness.getLocalState(),
   x: 167,
@@ -91,20 +91,26 @@ import {
 
 const store = new EphemeralStore();
 // Set ephemeral data
-store.set("loro-prosemirror", {
-    anchor: ...,
-    focus: ...,
+store.set("user-alice", {
+    anchor: 10,
+    focus: 20,
     user: "Alice"
 });
-store.set("online-users", ["Alice", "Bob"]);
 
-expect(storeB.get("online-users")).toEqual(["Alice", "Bob"]);
 // Encode only the data for `loro-prosemirror`
-const encoded = store.encode("loro-prosemirror")
-
-store.subscribe((e: EphemeralStoreEvent) => {
+const encoded = store.encode("user-alice")
+const newStore = new EphemeralStore();
+newStore.subscribe((e: EphemeralStoreEvent) => {
     // Listen to changes from `local`, `remote`, or `timeout` events
 });
+
+newStore.apply(encoded);
+console.log(newStore.get("user-alice"))
+// {
+//     anchor: 10,
+//     focus: 20,
+//     user: "Alice"
+// }
 ```
 
 ## Fix

pages/changelog/v1.5.0.mdx

@@ -204,7 +204,7 @@ The `onPush` and `onPop` callbacks are triggered when these stacks change:
 
 The `mergeInterval` option in the UndoManager controls how closely spaced operations are grouped:
 
-```ts
+```ts no_run
 const undoManager = new UndoManager(doc, {
   mergeInterval: 1000, // 1000ms = 1 second (default)
 });