- Updated protobufjs from ^7.2.4 to ^8.0.0
- Updated protobufjs-cli from ^1.1.3 to ^2.0.0
- This resolves peer dependency conflicts
- Use --legacy-peer-deps flag when installing
https://claude.ai/code/session_015R3U3kiprQiNTTNNt31Sg6
Production server (vmi2736502) uses Node v20.20.0, not v22.
@types/node must match the lowest Node version we support.
Changed:
- @types/node: ^22.12.5 → ^20.19.33
Local dev may use Node 22, but types must be compatible with
production Node 20 to avoid runtime errors from missing APIs.
https://claude.ai/code/session_015R3U3kiprQiNTTNNt31Sg6
Changed libsignal dependency from "github:whiskeysockets/libsignal-node"
to "https://github.com/whiskeysockets/libsignal-node.git" to fix
GitHub Actions workflow failures.
The Yarn package manager was not respecting Git's global URL rewrite
configuration and was trying to use SSH (which failed with "Permission
denied (publickey)"). Using explicit HTTPS syntax ensures the dependency
is always fetched over HTTPS in CI environments.
https://claude.ai/code/session_015R3U3kiprQiNTTNNt31Sg6
Fixes GitHub Actions workflow "Update WAProto" failure.
Problem:
- GenerateStatics.sh was being executed from project root
- Script looks for ./WAProto.proto (relative to CWD)
- This resolves to <root>/WAProto.proto (doesn't exist)
- Should be <root>/WAProto/WAProto.proto
Error in CI:
```
Error: ENOENT: no such file or directory, open 'WAProto.proto'
Error: Cannot find module '.../fix-imports.js'
```
Solution:
Change script execution to run from WAProto/ directory:
- Before: "sh WAProto/GenerateStatics.sh" (runs from root)
- After: "cd WAProto && sh GenerateStatics.sh" (runs from WAProto/)
Now paths resolve correctly:
- ./WAProto.proto → <root>/WAProto/WAProto.proto ✅
- ./fix-imports.js → <root>/WAProto/fix-imports.js ✅https://claude.ai/code/session_01TvSrN9JmHZDdKMZDFWEcUS
Changed from HTTPS URL to GitHub shorthand format for better reliability:
- Before: "https://github.com/whiskeysockets/libsignal-node.git"
- After: "github:whiskeysockets/libsignal-node"
Why this is better:
✅ Native Yarn/NPM support (optimized resolution)
✅ No protocol conversion issues
✅ Works consistently across all environments (CI, dev, prod)
✅ Shorter and cleaner syntax
✅ Official recommended format for GitHub dependencies
This format is equivalent to git+https:// but without SSH conversion bugs.
Tested and recommended by Yarn docs for GitHub repos.
The root cause was simple: Yarn converts git+https:// to SSH.
Solution: Change package.json to use direct HTTPS URL
- Before: "git+https://github.com/whiskeysockets/libsignal-node"
- After: "https://github.com/whiskeysockets/libsignal-node.git"
This eliminates SSH conversion completely and works with all package managers.
Also simplified workflow by removing unnecessary workarounds:
- Removed temporary package.json patching step
- Removed retry logic
- Restored simple 'yarn install --immutable'
Clean, permanent solution. 🎯
Surgically applies the changes from WhiskeySockets/Baileys commit b5c1741
("feat: replace async crypto with sync Rust WASM" by jlucaso1) while
preserving all custom modifications (interactive messages, carousels,
albums, sticker packs, native flow buttons, Prometheus metrics, etc).
Changes:
- Replace async hkdf/md5 (Web Crypto API) with sync re-exports from whatsapp-rust-bridge@0.5.2
- Replace LTHash class with LTHashAntiTampering from WASM
- Replace mutationKeys() with expandAppStateKeys() from WASM
- Remove ~25 unnecessary await keywords across crypto call chain
- Update Buffer→Uint8Array types for MediaDecryptionKeyInfo and internal crypto functions
- Make noise handshake, media retry encrypt/decrypt, and reporting token generation synchronous
Performance impact:
- Eliminates Promise overhead on every HKDF/LTHash operation
- Significant improvement during app state sync (hundreds of mutations per reconnection)
- Sync crypto reduces event loop pressure under high session load
Custom code preserved (zero conflicts):
- messages-send.ts: All interactive message, carousel, album, sticker pack logic intact
- Types/Message.ts: All custom types (NativeFlowButton, Carousel, Album, etc.) intact
- All Prometheus metrics, circuit breakers, session TTL logic intact
https://claude.ai/code/session_01Ffc5YrPuqv8N9SwEuSM8mr
- Add prom-client ^15.1.3 as production dependency
- Migrate Counter class to use prom-client internally
- Migrate Gauge class to use prom-client internally
- Migrate Histogram class to use prom-client internally
- Update getMetricsOutput() to use prom-client's native metrics()
- Update contentType() to use prom-client's contentType
- Enable collectDefaultMetrics() for Node.js system metrics
- Maintain backward compatibility with existing API
Benefits:
- Native OpenMetrics format export
- Proper histogram bucket handling
- Default Node.js metrics (memory, CPU, event loop, GC)
- Better integration with Grafana/Prometheus ecosystem
* lid-mapping: get missing lid from usync
* lid-mapping, jid-utils: change to isPnUser and store multiple mappings
* process-message: parse protocolMsg mapping, and store from new msgs
* types: lid-mapping event, addressing enum, alt, contact, group types
* validate, decode: use lid for identity, better logic
* lid: final commit
* linting
* linting
* linting
* linting
* misc: fix testing and also remove version json
* lint: IDE fucking up lint
* lid-mapping: fix build error on NPM
* message-retry: fix proto import
* Add message retry manager for session recreation and caching
Introduces a MessageRetryManager to cache recent sent messages and manage automatic Signal session recreation for failed message retries. Adds new config options to enable these features, integrates retry manager into message send/receive logic, and provides periodic cache cleanup. Improves reliability of message delivery and retry handling.
* Add buffer timeout and cache limit to event-buffer
Introduces a buffer timeout to auto-flush events after 30 seconds and limits the history cache size to prevent memory bloat in event-buffer.ts.
* Add session validation to SignalRepository
Introduces a validateSession method to SignalRepository for checking session existence and state. Updates message retry logic to use the new validation, improving session recreation handling and retry management.
* Improve message retry management and tracking
Refactored message retry manager to use LRU caches for recent messages and session history, added retry counters and statistics tracking, and implemented phone request scheduling. Updated message receive and send logic to mark retry success and pass max retry count. Removed periodic cleanup logic in favor of cache TTLs for better resource management.
* lint fix
* Use validateSession for session checks in message send
Replaces direct session existence checks with the improved validateSession method, which also checks for session staleness. Adds debug logging for failed session validations to aid troubleshooting.
* Delete src/Utils/message-retry.ts
---------
Co-authored-by: Rajeh Taher <rajeh@reforward.dev>
* feat: implement state machine for chat synchronization and buffer management
* test: Add Jest configuration and tests for connection deadlock handling
- Created a Jest configuration file to set up testing environment.
- Implemented utility functions for creating isolated authentication sessions and mocking WebSocket connections.
- Added a test case to ensure that the connection does not deadlock when history sync is disabled, verifying the correct handling of message events.
* feat: add GitHub Actions workflow for running tests
* chore: sort import lint
* fix: implement timeout handling for AwaitingInitialSync state in chat socket, maybe fix memory leak
* feat: enhance chat synchronization by refining AwaitingInitialSync handling and adding history sync checks
**Fix Windows path issue in `build` script**
**Issue**
The `build` script in `package.json` was written as:
```json
"build": "tsc -P tsconfig.build.json && tsc-esm-fix --tsconfig='tsconfig.build.json' --ext='.js'"
```
This works on Unix-based systems (macOS/Linux) but **breaks on Windows**, throwing an error:
```
Error: ENOENT: no such file or directory, open 'C:\path\to\project\'tsconfig.build.json''
```
> The single quotes `'` are treated **literally** on Windows CMD/PowerShell, resulting in a malformed path (e.g., `'tsconfig.build.json'` instead of `tsconfig.build.json`).
**Fixes**
Updated the script to remove single quotes around the `--tsconfig` and `--ext` arguments:
```json
"build": "tsc -P tsconfig.build.json && tsc-esm-fix --tsconfig=tsconfig.build.json --ext=.js"
```
**Result**
```
PS C:\Users\Astro\Documents\GitHub\Baileys> npm run build
> baileys@6.7.18 build
> tsc -P tsconfig.build.json && tsc-esm-fix --tsconfig=tsconfig.build.json --ext=.js
PS C:\Users\Astro\Documents\GitHub\Baileys>
```
Renato Alcara