// the find
wwebjs/whatsapp-web.js
A WhatsApp client library for NodeJS that connects through the WhatsApp Web browser app
whatsapp-web.js wraps a headless Chromium instance via Puppeteer to drive the actual WhatsApp Web client, exposing a Node.js API for sending/receiving messages, media, polls, and managing groups. It's for developers who want to build WhatsApp bots or integrations without access to WhatsApp's official (and expensive, business-gated) Cloud API.
Feature coverage is genuinely wide — groups, polls, channels, reactions, mentions, contact cards, location, multiple media types — it tracks the actual WhatsApp Web client closely rather than a stripped-down subset. Pluggable auth strategies (LocalAuth, RemoteAuth, NoAuth) handle session persistence sensibly, including a RemoteAuth path for stateless/containerized deployments. The project has real engineering hygiene around it: lint/test CI, husky + commitlint enforcing conventional commits, dependabot, and an automated release pipeline — this isn't a repo that was thrown over the wall.
The core architecture is inherently fragile: it works by puppeting a browser and reaching into WhatsApp Web's internal JS objects, so any client-side update from WhatsApp can silently break functionality until maintainers patch it — this is a structural risk baked into the approach, not a bug to fix. The README is upfront that this isn't an official or sanctioned integration and that account blocks are a real possibility, which is a hard constraint for anyone trying to build something reliable on top of it. Running a full Chromium instance per session makes it heavy on memory and CPU, so scaling to many concurrent accounts gets expensive fast compared to a real API client. The feature table also shows churn rather than stability — buttons and lists are already deprecated due to upstream changes, and Communities support is still just a 🔜, so the surface area you build against today isn't guaranteed to hold.