feat(server): run the WhatsApp channel on whatsapp-web.js (P1.7)
Baileys depends on libsignal (GPL-3.0), which the sidecar bundled. The WhatsApp adapter now drives WhatsApp Web through whatsapp-web.js and keeps its public shape: start, stop, status with the pairing QR, send and inbound text. LocalAuth stores the session as a browser profile in <dataDir>/channels/whatsapp; the old Baileys state is left untouched. The browser comes from whatsapp-browser.ts: CHROME_PATH or PUPPETEER_EXECUTABLE_PATH, then an installed Chrome, Edge or Chromium (Windows, macOS, Linux), then a Chrome for Testing build downloaded on the first start into <dataDir>/browsers, with progress in the status. The root .puppeteerrc.cjs stops npm install from downloading a browser. The sidecar build keeps whatsapp-web.js external: bundled, it fails on __dirname and would inline LGPL node-webpmux. Text only, so ffmpeg is never needed. New dependencies, pinned: whatsapp-web.js 1.34.7 (Apache-2.0) and @puppeteer/browsers 2.13.0 (Apache-2.0). Transitive: puppeteer, puppeteer-core, chromium-bidi, webdriver-bidi-protocol (Apache-2.0), devtools-protocol (BSD-3-Clause), extract-zip (BSD-2-Clause), fluent-ffmpeg and the rest (MIT or ISC), and node-webpmux (LGPL-3.0-or-later, shipped as a separate package; needs the license review). Removed: @whiskeysockets/baileys and libsignal. UF-020 is now Fixed; ADR-0005 records the consequences.
This commit is contained in:
@@ -132,6 +132,12 @@ const EXTERNAL = [
|
||||
'@playwright/*',
|
||||
'chromium-bidi',
|
||||
'chromium-bidi/*',
|
||||
// WhatsApp channel (ADR-0005). whatsapp-web.js is CommonJS that relies on
|
||||
// __dirname and fails inside the ESM bundle; bundling it would also inline
|
||||
// its LGPL-3.0 dependency node-webpmux and unused optional code (TypeScript,
|
||||
// the AWS S3 client). Staged as separate packages instead.
|
||||
'whatsapp-web.js',
|
||||
'@puppeteer/browsers',
|
||||
];
|
||||
|
||||
try {
|
||||
|
||||
Reference in New Issue
Block a user