fix: starting from v1.8 events are emitted synchronously

Author: zxch3n

pages/docs/api/js.mdx

@@ -37,9 +37,7 @@ Note: Under the hood, Loro combines a Fugue-based CRDT core with Eg-walker-inspi
 - Initialize all child containers for a LoroMap upfront when possible
 - Operations on the root containers will not override each other  
 
-**Events & Transactions**
-
-- Events emit asynchronously after a microtask in JS API
+- Events emit synchronously during commit/import/checkout in JS API (v1.8+). Stay on <=1.7.x? Await a microtask before reading batched events.
 - Import/export/checkout trigger automatic commits
 - Loro transactions are NOT ACID - no rollback/isolation
 
@@ -799,7 +797,7 @@ const forkedDoc = doc.forkAt(frontiers);
 
 ## Events & Transactions
 
-React to changes and group local operations into transactions. Events are delivered asynchronously after a microtask. See [Event Handling](/docs/tutorial/event) and [Transaction Model](/docs/concepts/transaction_model).
+React to changes and group local operations into transactions. Starting in v1.8, events are delivered synchronously; older releases require awaiting a microtask. See [Event Handling](/docs/tutorial/event) and [Transaction Model](/docs/concepts/transaction_model).
 
 ### Subscription Methods
 
@@ -844,11 +842,11 @@ const unsubscribe = doc.subscribe((event) => {
 // Later: unsubscribe();
 ```
 
-**⚠️ Important:** Events are emitted asynchronously after a microtask. 
+**⚠️ Important:** Events are emitted synchronously as of v1.8. If you are pinned to <=1.7.x, await a microtask before reading the batch.
 ```ts no_run
 doc.commit();
-await Promise.resolve();
-// Now events have been emitted
+// Events have already been delivered in v1.8+
+// await Promise.resolve(); // Only needed on <=1.7.x
 ```
 
 **📝 Note:** Multiple operations before a commit are batched into a single event. See [Event Handling](/docs/tutorial/event).

pages/docs/tutorial/event.mdx

@@ -19,7 +19,7 @@ with changes in the document state.
    - When `LoroDoc.commit()` is explicitly called
    - Automatically before an import or export operation
 
-   Note that events are emitted asynchronously after a microtask. If you need to handle events immediately after a commit, you should await a microtask:
+Starting from `[email protected]`, events are emitted synchronously during the commit cycle. If you are using an older version (<=1.7.x), you will still need to await a microtask for the callbacks to fire.
 
 ```ts no_run twoslash
 import { LoroDoc } from "loro-crdt";
@@ -32,9 +32,7 @@ doc.subscribe((event) => {
 const text = doc.getText("text");
 text.insert(0, "Hello");
 doc.commit();
-// Event hasn't been emitted yet
-await Promise.resolve();
-// Now the event has been emitted
+// Event has already been emitted synchronously
 ```
 
 3. **Import**: When importing changes from a remote source using the `import()`
@@ -50,21 +48,19 @@ doc.subscribe((event) => {
   console.log("Event:", event);
 });
 
-doc.import(remoteChanges); // This will trigger events after a microtask
-await Promise.resolve(); // Wait for events to be emitted
+doc.import(remoteChanges); // This immediately triggers events (v1.8+)
 ```
 
 4. **Version Checkout**: When you switch document state to a different version
    using `doc.checkout(frontiers)`, Loro emits an event to reflect this change.
-   Like other events, these are also emitted after a microtask.
+   As of v1.8, checkout events fire synchronously alongside the state change.
 
 ```ts no_run twoslash
 import { LoroDoc } from "loro-crdt";
 // ---cut---
 const doc = new LoroDoc();
 const frontiers = doc.frontiers();
-doc.checkout(frontiers); // This will trigger events after a microtask
-await Promise.resolve(); // Wait for events to be emitted
+doc.checkout(frontiers); // This triggers events immediately (v1.8+)
 ```
 
 ## Transaction Behavior