Migration Guide

AunuBaileys is built on the official @whiskeysockets/baileys 6.7.24 base — migrating is deliberately boring.

From @whiskeysockets/baileys

// 1. Swap the dependency
npm uninstall @whiskeysockets/baileys
npm i aunubaileys

// 2. Change the import specifier — nothing else
import makeWASocket, { useMultiFileAuthState } from 'aunubaileys'

Session compatibility: the auth state format is upstream's — point useMultiFileAuthState at your existing auth folder and the bot reconnects without re-pairing. (Back the folder up first; you should be doing that anyway.)

What you gain on day one

Capability	Upstream 6.7.24	AunuBaileys
`makeInMemoryStore`	Removed	✅ Restored, typed, loadMessage/toJSON/fromJSON — Store
`processedMessages`, `initInMemoryKeyStore()`, `PHONENUMBER_MCC`	Removed	✅ Restored — old scripts run unmodified
Sticker packs / albums via sendMessage	—	✅ 1.0.2 — Messages
Newsletter media uploads	Broken paths	✅ Fixed 1.0.2
Atomic session writes	—	✅ 1.0.2
Interactive builders (Button, Carousel, AIRich…)	—	✅ 1.0.4 — Builders
Anti-ban layer	—	✅ 1.0.5 — AunuAntiBan
Socket extras (`aunuHandler`, reachout timelock, chat cap…)	—	✅ 1.0.3 — API Reference

From community forks (itsliaaa, neoxr, MichelleBot, and friends)

Your features are probably already here. The headline features of those forks — sticker packs, albums, newsletter media fixes, the AI label, pre-key timeouts — were merged into AunuBaileys 1.0.2 with credit, then extended in 1.0.3–1.0.5. Check the changelog before porting anything by hand.
Fork-specific helper names won't exist. Anything that wasn't upstream or an AunuBaileys export needs porting to sendMessage content forms or the builders. The API Reference is the ground truth for what exists.
Sessions: auth folders from upstream-based forks are the same format — back up, swap, reconnect. If a fork modified its auth layout, pair fresh instead of debugging a half-migrated session.
One warning that matters: some rebranded Baileys forks circulating on npm are documented malware (the ourin-baileys package is the known case). If you're migrating from anything you didn't audit, pair a fresh session on the new install — don't carry credentials produced under code you can't trust. AunuBaileys itself is a clean-room, fully readable codebase: audit it the same way.

From Baileys 6.6.x / older

Your code likely already uses makeInMemoryStore — which is exactly why this package exists. Swap the dependency as above; the store API you remember (bind, loadMessage, toJSON/fromJSON) is the API that's here. Everything else follows the 6.7.x upstream surface.

Migration checklist

☐ Back up the auth folder
☐ Swap dependency, change import specifiers ('aunubaileys')
☐ Node ≥ 20 (the package enforces it)
☐ Reconnect once; confirm no 401/500 (if either appears, pair fresh — the old session was already damaged)
☐ Wire getMessage to the store if you hadn't (fixes "waiting for this message")
☐ Wrap with wrapAntiBan before any bulk sending
☐ Delete the old fork's patch files/shims — mixed helpers are the #1 source of ghost bugs after a swap