@antzsoft/chat-core 1.1.4 → 1.1.6

package/docs/integration-guide.html

@@ -155,7 +155,7 @@ section.sec>h2:hover{color:#fff}
 
   <div class="section-label">What's New</div>
   <ul>
-    <li><a href="#whats-new">v1.1.4 Release Notes</a></li>
+    <li><a href="#whats-new">v1.1.6 Release Notes</a></li>
   </ul>
 
   <div class="section-label">Getting Started</div>
@@ -242,16 +242,185 @@ section.sec>h2:hover{color:#fff}
   <h2>What's New</h2>
   <p style="color:var(--muted);font-size:13px;margin-bottom:20px">Version history and release notes. Click a version to expand.</p>
 
-  <!-- ── v1.1.4 (current) ── -->
-  <div class="wn-version open" id="wn-114">
-    <div class="wn-header" onclick="toggleVersion('wn-114')">
+  <!-- ── v1.1.6 (current) ── -->
+  <div class="wn-version open" id="wn-116">
+    <div class="wn-header" onclick="toggleVersion('wn-116')">
       <div class="wn-title">
-        <span class="wn-ver">v1.1.4</span>
+        <span class="wn-ver">v1.1.6</span>
         <span class="wn-badge current">Current</span>
         <span class="wn-date">May 2026</span>
       </div>
       <span class="wn-chevron">▲</span>
     </div>
+    <div class="wn-body">
+
+      <div class="wn-item" id="wn-116-1">
+        <div class="wn-item-header" onclick="toggleItem('wn-116-1')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Messages arrive out of order when typing and sending rapidly</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>When a user sent 10–15+ messages in quick succession, the SDK fired all <code>send_message</code> socket emits concurrently. Each emit raced independently against the 5-second ACK timeout, and the server received them in an unpredictable order — causing messages to appear jumbled in the recipient's view, even though the sender saw them in the correct order locally.</p>
+          <p>The SDK now routes all outgoing messages through a per-conversation FIFO send queue. The next message is only emitted after the server acknowledges the previous one, guaranteeing the server processes them in the exact order the user sent them. Two safety limits are enforced:</p>
+          <ul>
+            <li><strong>Max queue size: 100 entries per conversation.</strong> Any send beyond the limit is rejected immediately with an error so the caller can surface feedback rather than silently dropping messages.</li>
+            <li><strong>Per-entry TTL: 30 seconds.</strong> An entry that has been waiting in the queue longer than 30 seconds is dropped before it reaches the socket, preventing stale messages from arriving at the server long after the user typed them.</li>
+          </ul>
+          <p><strong>No integration changes required.</strong> The queue is applied automatically in <code>@antzsoft/chat-core</code> for both web and React Native SDKs.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-116-2">
+        <div class="wn-item-header" onclick="toggleItem('wn-116-2')">
+          <span class="wn-tag new">New</span>
+          <span class="wn-item-title">POST mirrors for all PUT and DELETE endpoints</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Every <code>PUT</code> and <code>DELETE</code> route on the server now has an equivalent <code>POST</code> endpoint running alongside it. This is required for deployments behind black-box proxies, carrier-grade NATs, and enterprise middleware stacks (common in Jio, Reliance, and similar infrastructure) that strip or block non-POST/GET HTTP methods.</p>
+          <p>The SDK calls the POST mirrors exclusively from this version onwards. The original <code>PUT</code>/<code>DELETE</code> routes remain fully operational — nothing is removed — so direct REST clients, third-party integrations, and older SDK versions are unaffected.</p>
+          <p>The POST mirror paths follow a consistent naming pattern:</p>
+          <ul>
+            <li><code>PUT /messages/:id</code> → <code>POST /messages/:id/update</code></li>
+            <li><code>DELETE /messages/:id</code> → <code>POST /messages/:id/delete</code></li>
+            <li><code>DELETE /messages/:id/for-me</code> → <code>POST /messages/:id/delete-for-me</code></li>
+            <li><code>DELETE /messages/:id/reactions/:emoji</code> → <code>POST /messages/:id/reactions/:emoji/remove</code></li>
+            <li><code>DELETE /messages/:id/star</code> → <code>POST /messages/:id/unstar</code></li>
+            <li><code>DELETE /messages/:id/pin</code> → <code>POST /messages/:id/unpin</code></li>
+            <li><code>PUT /conversations/:id</code> → <code>POST /conversations/:id/update</code></li>
+            <li><code>DELETE /conversations/:id</code> → <code>POST /conversations/:id/delete</code></li>
+            <li><code>DELETE /conversations/:id/leave</code> → <code>POST /conversations/:id/leave</code></li>
+            <li><code>DELETE /conversations/:id/participants/:userId</code> → <code>POST /conversations/:id/participants/:userId/remove</code></li>
+            <li><code>PUT /conversations/:id/participants/:userId/role</code> → <code>POST /conversations/:id/participants/:userId/role</code></li>
+            <li><code>DELETE /conversations/:id/mute</code> → <code>POST /conversations/:id/unmute</code></li>
+            <li><code>DELETE /conversations/:id/pin</code> → <code>POST /conversations/:id/unpin</code></li>
+            <li><code>PUT /conversations/:id/icon</code> → <code>POST /conversations/:id/icon</code></li>
+            <li><code>DELETE /conversations/:id/icon</code> → <code>POST /conversations/:id/icon/remove</code></li>
+            <li><code>PUT /users/me</code> → <code>POST /users/me/update</code></li>
+            <li><code>PUT /users/me/preferences</code> → <code>POST /users/me/preferences</code></li>
+            <li><code>PUT /users/me/password</code> → <code>POST /users/me/password</code></li>
+            <li><code>PUT /users/me/avatar</code> → <code>POST /users/me/avatar</code></li>
+            <li><code>DELETE /users/me/devices/:deviceId</code> → <code>POST /users/me/devices/:deviceId/remove</code></li>
+            <li><code>DELETE /users/me/blocked/:userId</code> → <code>POST /users/me/blocked/:userId/remove</code></li>
+            <li><code>DELETE /users/me/contacts/:userId</code> → <code>POST /users/me/contacts/:userId/remove</code></li>
+            <li><code>PUT /storage/direct-upload</code> → <code>POST /storage/direct-upload</code></li>
+            <li><code>DELETE /storage/files/:id</code> → <code>POST /storage/files/:id/delete</code></li>
+          </ul>
+          <p><strong>No integration changes required.</strong> The SDK handles this transparently. All mirror endpoints return the same HTTP status codes and response shapes as their originals, verified by an automated parity script.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-116-3">
+        <div class="wn-item-header" onclick="toggleItem('wn-116-3')">
+          <span class="wn-tag new">New</span>
+          <span class="wn-item-title"><code>lastReaction</code> on <code>lastMessage</code> in conversation responses</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p><code>Conversation.lastMessage</code> now includes a <code>lastReaction</code> field reflecting the most recent reaction added to the last message in the conversation.</p>
+          <p>Shape: <code>{ emoji: string; userId: string; displayName: string } | null</code>. The field is <code>null</code> when the last message has no reactions, or when the conversation has no messages.</p>
+          <p>This enables conversation list UIs to surface reaction activity inline — for example, rendering <em>"👍 Alice reacted"</em> as the conversation subtitle — without requiring a separate message fetch. The <code>lastReaction</code> field was already present on individual <code>Message</code> objects; it is now also propagated to the <code>lastMessage</code> snapshot on the <code>Conversation</code> object.</p>
+          <p><strong>No action required.</strong> The field is additive. Existing code that ignores unknown fields is unaffected.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-116-4">
+        <div class="wn-item-header" onclick="toggleItem('wn-116-4')">
+          <span class="wn-tag improvement">Improvement</span>
+          <span class="wn-item-title">Query optimisations — conversation list, message pagination, unread counts</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Several high-traffic database queries have been rewritten with targeted compound indexes covering the most common access patterns:</p>
+          <ul>
+            <li><strong>Conversation list</strong> — the <code>GET /conversations</code> query (filtered by tenant, user, pinned/muted/unread state, type, role, and attachment presence) now uses a purpose-built compound index. Load times are significantly reduced for tenants with large participant or conversation counts.</li>
+            <li><strong>Message pagination</strong> — cursor-based before/after pagination on <code>GET /conversations/:id/messages</code> uses a tighter index that avoids full collection scans on high-volume conversations.</li>
+            <li><strong>Unread count aggregation</strong> — <code>GET /conversations/unread</code> and per-conversation unread counts now run against an optimised index, reducing latency on app cold start and foreground resume.</li>
+          </ul>
+          <p>No API surface changes. No integration changes required.</p>
+        </div>
+      </div>
+
+    </div>
+  </div><!-- /.wn-version -->
+
+  <!-- ── v1.1.5 ── -->
+  <div class="wn-version" id="wn-115">
+    <div class="wn-header" onclick="toggleVersion('wn-115')">
+      <div class="wn-title">
+        <span class="wn-ver">v1.1.5</span>
+        <span class="wn-date">May 2026</span>
+      </div>
+      <span class="wn-chevron">▼</span>
+    </div>
+    <div class="wn-body">
+
+      <div class="wn-item" id="wn-115-1">
+        <div class="wn-item-header" onclick="toggleItem('wn-115-1')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Hermes crash on image upload — <code>crypto.randomUUID()</code> unavailable on React Native</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Hermes (React Native's JS engine) does not expose <code>globalThis.crypto.randomUUID</code>, causing a hard crash whenever <code>uploadBatch</code> was called on iOS or Android — including all image and file attachments.</p>
+          <p>A new <code>generateUUID()</code> helper is included in <code>@antzsoft/chat-core</code> that uses the Web Crypto API when available and falls back to a <code>Math.random</code>-based RFC 4122 v4 UUID on environments that lack it (Hermes, older Node). It is used in <code>uploadBatch</code>, the RN <code>useChat</code> hook, and the web <code>useChat</code> hook.</p>
+          <p><strong>No action required.</strong> The fix is applied automatically. No integration changes needed.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-115-2">
+        <div class="wn-item-header" onclick="toggleItem('wn-115-2')">
+          <span class="wn-tag fix">Fix</span>
+          <span class="wn-item-title">Batch upload slot misalignment when a file fails presigned-URL generation</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>When one or more files in a batch failed the presigned-URL request, the SDK's slot-mapping logic was incorrect. The previous implementation assumed failed entries appear at the end of the server's <code>errors</code> array — but the server processes files in order, so a failure at position 1 produced <code>urls = [file0, file2]</code> and <code>errors = [file1]</code>, causing the SDK to assign file2's presigned URL to the wrong slot and corrupt upload-to-UI tracking.</p>
+          <p>The fix introduces a <code>clientIndex</code> — a 0-based position sent with each file in the batch request. The server now echoes it back in both <code>urls</code> and <code>errors</code> entries. The SDK uses the echoed <code>clientIndex</code> for all slot resolution. This is reliable regardless of failure pattern, file count, or whether multiple files share the same name. A filename-based fallback is kept for older server versions that do not echo the index.</p>
+          <p><strong>No integration changes required.</strong> Callers of <code>uploadBatch</code> and <code>uploadBatchWithSlots</code> are unaffected.</p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-115-3">
+        <div class="wn-item-header" onclick="toggleItem('wn-115-3')">
+          <span class="wn-tag improvement">Improvement</span>
+          <span class="wn-item-title">Conversation list reaction counts update live without a full refetch</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p><code>SocketProvider</code> in both the web SDK and RN SDK now handles <code>reaction_updated</code> socket events by patching the affected conversation's <code>lastMessage.reactions</code> directly in the local conversations cache.</p>
+          <p>Previously, emoji counts on the conversation list were stale until the next full list refresh or navigation. The count now updates immediately when any reaction is added or removed in any conversation — including conversations that are not currently open.</p>
+          <p><strong>No integration changes required.</strong></p>
+        </div>
+      </div>
+
+      <div class="wn-item" id="wn-115-4">
+        <div class="wn-item-header" onclick="toggleItem('wn-115-4')">
+          <span class="wn-tag improvement">Improvement</span>
+          <span class="wn-item-title">Server — <code>conversation_updated</code> fan-out and create conversation batch-optimised</span>
+          <span class="wn-chevron-sm">▾</span>
+        </div>
+        <div class="wn-item-body">
+          <p>Two server-side performance improvements with no API surface changes:</p>
+          <p><strong>Fan-out batch query.</strong> When a conversation update was broadcast to all participants (on message, reaction, role change, member add/remove), the server previously ran 3 sequential DB queries per participant to build each recipient's response DTO — 300 round trips for a 100-member group. The fan-out now runs a single batch: 1 participants query, 1 batch user lookup, 1 batch read-receipt query, then parallel unread counts — one shared DTO emitted to all recipients.</p>
+          <p><strong>Create conversation fire-and-forget.</strong> <code>POST /conversations</code> previously awaited the full <code>conversation_created</code> socket fan-out before returning the HTTP response. For 300 participants this triggered ~900 DB queries before the caller received a reply. The broadcast is now fire-and-forget with a single shared DTO built once and emitted to all participants in memory. The API responds immediately after the conversation is written.</p>
+          <p><strong>No API or integration changes required.</strong></p>
+        </div>
+      </div>
+
+    </div>
+  </div><!-- /.wn-version -->
+
+  <!-- ── v1.1.4 ── -->
+  <div class="wn-version" id="wn-114">
+    <div class="wn-header" onclick="toggleVersion('wn-114')">
+      <div class="wn-title">
+        <span class="wn-ver">v1.1.4</span>
+        <span class="wn-date">May 2026</span>
+      </div>
+      <span class="wn-chevron">▼</span>
+    </div>
     <div class="wn-body">
 
       <div class="wn-item" id="wn-114-1">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@antzsoft/chat-core",
-  "version": "1.1.4",
+  "version": "1.1.6",
   "description": "Platform-agnostic core for Antz Chat — API, socket, stores, types. Works in browser, React Native (Expo or bare), and Node.js.",
   "author": "Antz",
   "license": "MIT",
@@ -13,6 +13,11 @@
       "types": "./dist/index.d.ts",
       "import": "./dist/index.js",
       "require": "./dist/index.cjs"
+    },
+    "./internal": {
+      "types": "./dist/internal.d.ts",
+      "import": "./dist/internal.js",
+      "require": "./dist/internal.cjs"
     }
   },
   "files": [