Private maintained build source for WhatsApp integration
  • JavaScript 99.5%
  • Shell 0.5%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Adi1231234 1780711a1c
fix: prevent duplicate ready events on SPA re-injection (#201653)
* fix: prevent duplicate ready events on SPA re-injection

1. Add _injectInProgress concurrency guard
2. Replace polling loops with waitForFunction
3. Deduplicate Backbone listeners via tuple array with cleanup
4. Atomic hasSynced check after listener registration
5. isMainFrame guard and storeAvailable SPA skip in framenavigated

co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: add robustness fixes from fork PR #41

- try/finally around inject() to always reset _injectInProgress
- Atomic hasSynced check inside listener registration evaluate()
- Fix framenavigated: capture isLogout before async, skip re-inject
  only when not logout AND store available
- try/catch around obj.off() in listener cleanup
- Null guard in QR ref change handler
- Reset qrRetries on LOADING_SCREEN event
- Add exposeFunctionIfAbsent in requestPairingCode()

co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: remove QR listener on auth success

extract named onRefChange handler so it can be removed via
socket.on('change:hasSynced') once authentication succeeds,
matching PR #41's cleanup behavior.

co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* refactor: remove exposeFunctionIfAbsent from requestPairingCode

* fix: run refreshQR in browser context via pupPage.evaluate

the onAuthAppStateChangedEvent callback is registered with
exposefunctionifabsent, so it runs in Node.js context, not the browser.
calling window.require() there throws ReferenceError: window is not defined,
which means the QR code was never refreshed on UNPAIRED_IDLE state.

* fix: remove unnecessary try/catch around Backbone .off()

backbone's .off() never throws - verified on a live WhatsApp Web
instance with non-existent listeners, fake events, and double-off.
the try/catch was defensive but unnecessary.

* fix: remove unnecessary try/catch blocks in framenavigated handler

- storeAvailable: evaluate() always succeeds after framenavigated
  because Puppeteer waits for the execution context automatically
  (verified via CDP event order and Puppeteer source)
- inject(): matches upstream behavior - let errors surface instead
  of silently swallowing them

* fix: use AbortController to cancel inject on page navigation

when WhatsApp Web does location.reload() during inject (e.g. after
viewer context auth), puppeteer's waitForFunction hangs for 30s on
a dead execution context. After the timeout, no recovery is possible.

fix:
- Replace _injectInProgress flag with AbortController pattern: new
  inject() calls automatically cancel any previous in-progress inject
- Pass signal to waitForFunction for immediate cancellation
- Move framenavigated handler registration before first inject() in
  initialize(), so navigation during startup triggers re-inject
- Abort inject on destroy() to prevent spurious errors

* chore: ignore *.d.ts in eslint

upstream added TypeScript declaration changes that ESLint cannot parse.

* chore: revert index.d.ts and .eslintignore changes

* fix: reset _framenavigatedRegistered flag on destroy

* fix: revert unintended setCurrentIndexHtml refactor from lint auto-fix

* fix: replace async listener with waitForResponse for index cache

the response listener used an async handler on EventEmitter. mitt
ignores returned Promises, so when res.text() rejected on CDP
disconnect the promise was orphaned - causing unhandledRejection.

replace with page.waitForResponse() which returns a proper Promise
chain. Use .catch((_) => _) following the existing convention in
this codebase (see waitForNavigation on line 386).

* Revert "fix: replace async listener with waitForResponse for index cache"

This reverts commit 8cfd915ee5331d8b828c74ca8306dc72517bb0f1.

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-06-24 23:49:54 -03:00
.github fix(deps): upgrade eslint and plugins to 9.39.4 (#201701) 2026-04-18 17:50:05 -03:00
.husky chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
docs chore(v1.34.7): bump version and generate docs 2026-04-24 20:10:36 +00:00
src fix: prevent duplicate ready events on SPA re-injection (#201653) 2026-06-24 23:49:54 -03:00
tests fix(deps): upgrade eslint and plugins to 9.39.4 (#201701) 2026-04-18 17:50:05 -03:00
tools chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.editorconfig chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.env.example chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.gitattributes chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.gitignore fix: sendMessage with quoted message id (#3260) 2024-09-15 01:44:07 +03:00
.jsdoc.json chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.lintstagedrc.json chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.npmignore fix npmignore 2023-08-10 00:53:25 -04:00
.prettierignore chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.prettierrc.json chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
commitlint.config.js chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
eslint.config.mjs fix(deps): upgrade eslint and plugins to 9.39.4 (#201701) 2026-04-18 17:50:05 -03:00
example.js feat: support big file downloads (read from WA cache + streaming) (#201697) 2026-06-19 13:07:21 -03:00
index.d.ts feat: support big file downloads (read from WA cache + streaming) (#201697) 2026-06-19 13:07:21 -03:00
index.js chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
LICENSE Create LICENSE 2019-02-16 22:22:51 -04:00
package-lock.json chore(v1.34.7): bump version and generate docs 2026-04-24 20:10:36 +00:00
package.json chore(v1.34.7): bump version and generate docs 2026-04-24 20:10:36 +00:00
README.md fix: resolve naming issues (#201712) 2026-04-16 12:45:35 -03:00
shell.js chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00

About

whatsapp‑web.js is a powerful Node.js library that lets you interact with WhatsApp Web, making it easy to build a dynamic WhatsApp API with nearly all features of the web client. It uses Puppeteer to access WhatsApp Web’s internal functions and runs them in a managed browser instance to reduce the risk of being blocked.

Installation

Node.js v18.0.0 or higher, is required.

npm install whatsapp-web.js
yarn add whatsapp-web.js
pnpm add whatsapp-web.js

Having trouble installing? Take a peak at the Guide for more detailed instructions.

Example usage

const { Client } = require('whatsapp-web.js');
const qrcode = require('qrcode-terminal');

const client = new Client();

client.on('qr', (qr) => {
    qrcode.generate(qr, { small: true });
});

client.on('ready', () => {
    console.log('Client is ready!');
});

client.on('message', (msg) => {
    if (msg.body == '!ping') {
        msg.reply('pong');
    }
});

client.initialize();

Take a look at example.js for additional examples and use cases.
For more details on saving and restoring sessions, check out the Authentication Strategies.

Supported features

Feature Status
Multi Device ✅
Send messages ✅
Receive messages ✅
Send media (images/audio/documents) ✅
Send media (video) ✅ (requires Google Chrome)
Send stickers ✅
Receive media (images/audio/video/documents) ✅
Send contact cards ✅
Send location ✅
Send buttons ❌ (DEPRECATED)
Send lists ❌ (DEPRECATED)
Receive location ✅
Message replies ✅
Join groups by invite ✅
Get invite for group ✅
Modify group info (subject, description) ✅
Modify group settings (send messages, edit info) ✅
Add group participants ✅
Kick group participants ✅
Promote/demote group participants ✅
Mention users ✅
Mention groups ✅
Mute/unmute chats ✅
Block/unblock contacts ✅
Get contact info ✅
Get profile pictures ✅
Set user status message ✅
React to messages ✅
Create polls ✅
Channels ✅
Vote in polls ✅
Communities 🔜

Something missing? Make an issue and let us know!

Supporting the project

You can support the maintainer of this project through the links below:

Contributing

Feel free to open pull requests; we welcome contributions! However, for significant changes, it's best to open an issue beforehand. Make sure to review our contribution guidelines before creating a pull request. Before creating your own issue or pull request, always check to see if one already exists!

Disclaimer

This project is not affiliated, associated, authorized, endorsed by, or in any way officially connected with WhatsApp or any of its subsidiaries or its affiliates. The official WhatsApp website can be found at whatsapp.com. "WhatsApp" as well as related names, marks, emblems and images are registered trademarks of their respective owners. Also it is not guaranteed you will not be blocked by using this method. WhatsApp does not allow bots or unofficial clients on their platform, so this shouldn't be considered totally safe.

License

Copyright 2019 Pedro S Lopez

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this project except in compliance with the License.
You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.