aunubaileys 1.0.19 → 1.0.21

package/README.md

@@ -64,6 +64,14 @@ Everything else is pure upstream. When upstream moves, we rebase the patch layer
 
 
 
+### 🆕 What's new in 1.0.21 / Baru di 1.0.21
+
+- 💾 **saveCreds writes are coalesced** — during pairing, `creds.update` fires many times per second and every event used to queue a full atomic creds.json write. Concurrent `saveCreds()` calls now share one in-flight write, and a call landing mid-write schedules exactly one follow-up, so the file always ends with the latest creds — verified: a 30-call burst produced only ~2–3 real writes instead of 30.
+
+### 🆕 What's new in 1.0.20 / Baru di 1.0.20
+
+- ⏳ **Sends survive reconnect blips** — calling `sendMessage` while the connection is re-establishing used to fail instantly with a 428 from the first internal query, and the message was simply lost. `relayMessage` now waits for the transport to reopen (bounded by `connectTimeoutMs`; a permanently closed connection still fails fast, and a wait that expires raises a clear 408). When the connection is open, behaviour is unchanged.
+
 ### 🆕 What's new in 1.0.19 / Baru di 1.0.19
 
 - 🛟 **A failed retry request can no longer kill your bot** — the retry-receipt path after a decrypt failure runs fire-and-forget (by design), but its promise had no error handler at all: one failure inside it became an unhandled rejection, and Node's default policy terminates the whole process. It now routes to the standard error handler — logged, contained, and the bot keeps processing messages.

package/lib/Socket/messages-send.js

@@ -12,7 +12,7 @@ import { makeNewsletterSocket } from './newsletter.js';
 export const makeMessagesSocket = (config) => {
     const { logger, linkPreviewImageThumbnailWidth, generateHighQualityLinkPreview, options: axiosOptions, patchMessageBeforeSending, cachedGroupMetadata } = config;
     const sock = makeNewsletterSocket(makeGroupsSocket(config));
-    const { ev, authState, processingMutex, signalRepository, upsertMessage, query, fetchPrivacySettings, sendNode, groupMetadata, groupToggleEphemeral } = sock;
+    const { ev, authState, processingMutex, signalRepository, upsertMessage, query, fetchPrivacySettings, sendNode, groupMetadata, groupToggleEphemeral, ws, waitForSocketOpen } = sock;
     const userDevicesCache = config.userDevicesCache ||
         new NodeCache({
             stdTTL: DEFAULT_CACHE_TTLS.USER_DEVICES, // 5 minutes
@@ -269,6 +269,20 @@ export const makeMessagesSocket = (config) => {
         return { nodes, shouldIncludeDeviceIdentity };
     };
     const relayMessage = async (jid, message, { messageId: msgId, participant, additionalAttributes, additionalNodes, useUserDevicesCache, useCachedGroupMetadata, statusJidList }) => {
+        if (!ws.isOpen) {
+            // AunuBaileys: a send attempted during a reconnect window used to die
+            // instantly with Boom 428 from the first internal query — the message
+            // was simply lost unless the consumer retried. Now the send waits for
+            // the transport to reopen, bounded by connectTimeoutMs; a connection
+            // that closes for good still fails fast via waitForSocketOpen itself.
+            const waitMs = config.connectTimeoutMs ?? 60000;
+            await Promise.race([
+                waitForSocketOpen(),
+                delay(waitMs).then(() => {
+                    throw new Boom(`Timed out waiting ${waitMs}ms for the connection to open before sending`, { statusCode: 408 }); // 408 = DisconnectReason.timedOut
+                })
+            ]);
+        }
         const meId = authState.creds.me.id;
         let shouldIncludeDeviceIdentity = false;
         const { user, server } = jidDecode(jid);

package/lib/Utils/use-multi-file-auth-state.js

@@ -88,6 +88,8 @@ export const useMultiFileAuthState = async (folder) => {
     }
     const fixFileName = (file) => file?.replace(/\//g, '__')?.replace(/:/g, '-');
     const creds = (await readData('creds.json')) || initAuthCreds();
+    let credsWriteInFlight = null;
+    let credsWriteQueued = false;
     return {
         state: {
             creds,
@@ -117,7 +119,29 @@ export const useMultiFileAuthState = async (folder) => {
             }
         },
         saveCreds: async () => {
-            return writeData(creds, 'creds.json');
+            // AunuBaileys: coalesce the write bursts. creds.update fires many
+            // times per second during pairing (registration, pre-key uploads,
+            // identity pushes); upstream queued one full atomic write per call
+            // on the file mutex, so pairing did dozens of redundant full-file
+            // writes. Concurrent callers now share one in-flight write, and a
+            // call landing mid-write schedules exactly ONE follow-up write so
+            // the file always ends with the LATEST creds.
+            if (credsWriteInFlight) {
+                credsWriteQueued = true;
+                return credsWriteInFlight;
+            }
+            credsWriteInFlight = (async () => {
+                try {
+                    do {
+                        credsWriteQueued = false;
+                        await writeData(creds, 'creds.json');
+                    } while (credsWriteQueued);
+                }
+                finally {
+                    credsWriteInFlight = null;
+                }
+            })();
+            return credsWriteInFlight;
         }
     };
 };

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "aunubaileys",
   "type": "module",
-  "version": "1.0.19",
+  "version": "1.0.21",
   "description": "AunuBaileys \u2014 a WhatsApp Web API for bots that never sleep. Full upstream power with the beloved in-memory store restored and pairing that just works. Forged by AunuCore.",
   "keywords": [
     "whatsapp",