[core] Fix changelog version

fix #262

docs/site/content/en/docs/how-to/engines/index.md

@@ -78,7 +78,7 @@ For **x86** processors use following images:
 
 For **ARM** processors use following images:
 - `devlikeapro/whatsapp-http-api:arm` - **Chromium**
-- `devlikeapro/whatsapp-http-api:arm-noweb`- **no browser installed**
+- `devlikeapro/whatsapp-http-api:noweb-arm`- **no browser installed**
 
 {{< alert icon="💡" text="Chrome version is not available in ARM" />}}
 

docs/site/content/en/docs/overview/changelog.md

@@ -19,6 +19,9 @@ If you wish to get and read Release Notes - read them on one of our platforms, *
 
 You even can **subscribe to get new updates** there!
 
+## 2024.2
+- Listen for browser disconnected and page close events in **WEBJS** engine [#262](https://github.com/devlikeapro/whatsapp-http-api/issues/262)
+
 ## 2023.12
 December 2023
 - Add `chatId` field to `GET /api/contacts/check-exists` to help get the right `chatId` for Brazilian numbers.

docs/site/content/en/docs/overview/faq.md

@@ -14,6 +14,7 @@ toc: true
 ---
 
 ## How much CPU and Memory does WhatsApp HTTP API consume?
+### WEBJS
 
 The benchmark has been made on **Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz**.
 It may differ from case to case, it depends on usage pattern - how many messages you get, how many send, etc.
@@ -26,4 +27,10 @@ It may differ from case to case, it depends on usage pattern - how many messages
 The nature of WhatsApp HTTP API and its underlying engines - is to run **real** WhatsApp Web version in Chrome and
 communicate with it to prevent blocking from WhatsApp. It's the reason why it's so demanding on resources.
 
+### NOWEB
 If you're looking for less resource demanded engine - [have a look at **NOWEB** engine ->]({{< relref "/docs/how-to/engines" >}})
+
+The quote from the user:
+> The server has 2 CPU and 8GB of memory.
+> Today we have 85 session in this instance.
+

src/core/session.webjs.core.ts

@@ -99,11 +99,25 @@ export class WhatsappSessionWebJSCore extends WhatsappSession {
   async start() {
     this.status = WAHASessionStatus.STARTING;
     this.whatsapp = this.buildClient();
-    this.whatsapp.initialize().catch((error) => {
-      this.status = WAHASessionStatus.FAILED;
-      this.log.error(error);
-      return;
-    });
+    this.whatsapp
+      .initialize()
+      .then(() => {
+        // Listen for browser disconnected event
+        this.whatsapp.pupBrowser.on('disconnected', () => {
+          this.status = WAHASessionStatus.FAILED;
+          this.log.error('The browser has been disconnected');
+        });
+        // Listen for page close event
+        this.whatsapp.pupPage.on('close', () => {
+          this.status = WAHASessionStatus.FAILED;
+          this.log.error('The WhatsApp Web page has been closed');
+        });
+      })
+      .catch((error) => {
+        this.status = WAHASessionStatus.FAILED;
+        this.log.error(error);
+        return;
+      });
     if (this.isDebugEnabled()) {
       this.listenEngineEventsInDebugMode();
     }