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 6de0b0dd2b
fix: prevent store model mutation in getContact and getChatModel LID handling (#127098)
* fix: prevent store mutation in getContact/getChatModel LID handling

getcontact() and getChatModel() overwrite .id directly on live Backbone
model references from WhatsApp Web's Contact/Participant store. This
permanently corrupts the store for the lifetime of the session, causing
all subsequent lookups for the same contact to crash with:
- "Cannot read properties of undefined (reading '_serialized')"
- "Data passed to getter must include an id property"

the fix resolves LID to phone on the serialized copy only, never
touching the live store model.

fixes #127054

* perf: use BusinessProfile.find() instead of fetchBizProfile()

businessprofile.find() checks the local cache first and only fetches
from the server when the profile is missing, while fetchBizProfile()
always makes a network call (~85-100ms per contact). This significantly
reduces latency when getContact is called repeatedly for the same
business contacts.

closes #201656

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

* fix: remove unnecessary try/catch around BusinessProfile.find()

businessprofile.find() never throws for non-business contacts - it returns
a BusinessProfile model with profileOptions: null, not an error. The comment
was factually incorrect. The existing profileOptions guard handles the
non-business case correctly without any exception handling.

verified in WhatsApp Web DevTools: find() returns a valid object for regular,
business, LID, and even non-existent contacts. Only throws when called without
an id, which cannot happen here.

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

* refactor: simplify contact/chat model utils via native WA functions

replace the O(n²) LID participant loop with WAWebLidMigrationUtils.toPn()
which resolves LID WIDs via LidPnCache in O(1). Remove the findContact
wrapper since Contact.find() accepts strings directly. Use
wawebwidfactory.createWidFromWidLike() for safe isLid() calls that handle
plain-object contact ids without WID prototype methods.

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

* perf: skip BusinessProfile.find() for non-business contacts

wa's own source guards this behind isBusiness || isEnterprise
(WAWebUseBusinessProfile.react). No point querying business profiles
for regular contacts - saves a wasted IQ roundtrip (~80ms) per call.

* revert: remove block/unblock changes from this PR

moved to a dedicated PR (#201671) with a proper fix using
wawebblockcontactutils.getContactToBlockOnlyUseIfNoAssociatedChat()
for correct LID resolution.

* fix: convert contactId to Wid before collection find() calls

contact.find() and BusinessProfile.find() reject plain strings when
the entry is not cached or stale, throwing "gadd called without an id
attr". Use createWid(contactId) to ensure a proper Wid object is passed.

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-24 10:00:11 -03:00
.github chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.husky chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
docs chore(v1.34.6): bump version and generate docs 2026-01-30 16:40:01 +00:00
src fix: prevent store model mutation in getContact and getChatModel LID handling (#127098) 2026-03-24 10:00:11 -03:00
tests chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02: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
.eslintignore chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
.eslintrc.json 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
example.js chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
index.d.ts chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02: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.json chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
README.md chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02: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.