@wppconnect/wa-js 4.3.0 → 4.3.1

package/CHANGELOG.md

@@ -1,3 +1,3 @@
-## 4.3.0 (2026-05-19)
+## <small>4.3.1 (2026-06-19)</small>
 
-* build(deps-dev): update dependency @wppconnect/wa-version to ^1.5.3967 (#3459) ([399fa1478d6037c83ef4f6baadeea49e7944f1c8](https://github.com/wppconnect-team/wa-js/commit/399fa1478d6037c83ef4f6baadeea49e7944f1c8)), closes [#3459](https://github.com/wppconnect-team/wa-js/issues/3459)
+* fix(group): pass membershipApprovalMode to joinGroupViaInvite (#3468) ([3383b0374789dd25564068669bd2caadc25c0f5a](https://github.com/wppconnect-team/wa-js/commit/3383b0374789dd25564068669bd2caadc25c0f5a)), closes [#3468](https://github.com/wppconnect-team/wa-js/issues/3468) [#2221](https://github.com/wppconnect-team/wa-js/issues/2221)

package/README.md

@@ -483,6 +483,90 @@ This is useful for:
 - Identifying when function signatures changed
 - Finding new or removed modules
 
+## Building with a custom global variable name
+
+If you are developing an extension or automation tool that may run on the same WhatsApp Web page alongside other WA-JS-based projects, you can compile your own build of this library under a different global variable name to avoid conflicts.
+
+### When to do this
+
+By default, WA-JS exposes itself as `window.WPP`. If two tools built on WA-JS are injected into the same page using the default name, they will overwrite each other. Building under a custom name (e.g. `window.MYWPP`) ensures each tool owns its own isolated global.
+
+### Steps
+
+**1. Clone the repository and install dependencies**
+
+```bash
+git clone https://github.com/wppconnect-team/wa-js.git
+cd wa-js
+npm install
+```
+
+**2. Change the global variable name in `webpack.config.js`**
+
+Find the `output.library` block and replace `'WPP'` with your chosen name:
+
+```js
+// webpack.config.js
+output: {
+  filename: 'wppconnect-wa.js',
+  path: path.resolve(__dirname, 'dist'),
+  library: {
+    name: 'MYWPP', // <-- your custom global variable name
+    type: 'global',
+  },
+},
+```
+
+**3. Update the pre-injection config key in `src/config/index.ts`**
+
+Replace every occurrence of `WPPConfig` with `<YOURNAME>Config` (e.g. `MYWPPConfig`). There are three occurrences in that file:
+
+```ts
+// Before
+interface Window { WPPConfig: Config; }
+const setted = window.WPPConfig || {};
+window.WPPConfig = config;
+
+// After (using MYWPP as example)
+interface Window { MYWPPConfig: Config; }
+const setted = window.MYWPPConfig || {};
+window.MYWPPConfig = config;
+```
+
+**4. Build the production bundle**
+
+```bash
+npm run build:prd
+```
+
+The compiled file will be available at:
+
+```
+dist/wppconnect-wa.js
+```
+
+### Result
+
+When your custom build is injected into WhatsApp Web:
+
+- The library is available as **`window.MYWPP`** (your chosen name).
+- **`window.WPP` is not set** — there is no conflict with other WA-JS builds on the same page.
+- Pre-injection configuration is read from **`window.MYWPPConfig`** instead of `window.WPPConfig`.
+
+**Pre-injection usage example:**
+
+```javascript
+// Set this before injecting your custom build
+window.MYWPPConfig = {
+  deviceName: 'My Extension',
+};
+
+// After injection, use your custom global
+window.MYWPP.loader.onReady(function () {
+  console.log('My extension is ready');
+});
+```
+
 ## How to use this project
 
 Basically, you need to inject the `wppconnect-wa.js` file into the browser after WhatsApp page load.

package/dist/group/functions/join.d.ts

@@ -13,16 +13,32 @@
  * See the License for the specific language governing permissions and
  * limitations under the License.
  */
+/**
+ * Result returned by {@link join}.
+ *
+ * `pendingApproval` is `true` when the group has `membershipApprovalMode`
+ * enabled and the join request was submitted successfully but still requires
+ * an admin to approve it before the bot becomes a member.
+ */
+export interface JoinGroupResult {
+    id: string;
+    pendingApproval: boolean;
+}
 /**
  * Join in a group from an invite code.
  *
+ * When the group requires admin approval (`membershipApprovalMode: true`),
+ * the method returns `{ id, pendingApproval: true }` instead of throwing
+ * `UnexpectedJoinGroupViaInviteResponse` (issues #2221 / #2746).
+ *
  * @example
  * ```javascript
- * await WPP.group.join('abcde....');
+ * const result = await WPP.group.join('abcde....');
+ * if (result.pendingApproval) {
+ *   console.log('Request sent — waiting for admin approval');
+ * }
  * ```
  *
  * @category Group
  */
-export declare function join(inviteCode: string): Promise<{
-    id: string;
-}>;
+export declare function join(inviteCode: string): Promise<JoinGroupResult>;

package/dist/whatsapp/functions/joinGroupViaInvite.d.ts

@@ -16,7 +16,12 @@
 import { Wid } from '..';
 /**
  * @whatsapp 153438 >= 2.2301.5
+ *
+ * When `membershipApprovalMode` is `false` (default) the server must respond
+ * with a `<group>` node; when `true` it must respond with
+ * `<membership_approval_request>`.  If the wrong node is returned the function
+ * throws `UnexpectedJoinGroupViaInviteResponse` (see WAWebBackendErrors).
  */
-export declare function joinGroupViaInvite(groupId: Wid): Promise<{
+export declare function joinGroupViaInvite(code: string, membershipApprovalMode: boolean): Promise<{
     gid: Wid;
 }>;

package/dist/whatsapp/functions/sendJoinGroupViaInvite.d.ts

@@ -14,7 +14,18 @@
  * limitations under the License.
  */
 import { Wid } from '..';
+/**
+ * Result shape returned by {@link sendJoinGroupViaInvite}.
+ *
+ * `membershipApprovalMode` mirrors the flag queried via
+ * `getGroupInfoFromInviteCode` and signals whether the bot's join request is
+ * pending admin approval (`true`) or the bot joined immediately (`false`).
+ */
+export interface SendJoinGroupViaInviteResult {
+    gid: Wid;
+    membershipApprovalMode: boolean;
+}
 /** @whatsapp 69586
  * @whatsapp 769586 >= 2.2222.8
  */
-export declare function sendJoinGroupViaInvite(code: string): Promise<Wid>;
+export declare function sendJoinGroupViaInvite(code: string): Promise<SendJoinGroupViaInviteResult>;