Version 1.16.2

.editorconfig

@@ -4,5 +4,9 @@ root = true
 indent_style = space
 indent_size = 4
 charset = utf-8
-trim_trailing_whitespace = false
-insert_final_newline = false
+trim_trailing_whitespace = true
+insert_final_newline = true
+end_of_line = lf
+
+[*.md]
+trim_trailing_whitespace = false

.env.example

@@ -1,2 +1,2 @@
-WWEBJS_TEST_SESSION_PATH=test_session.json
-WWEBJS_TEST_REMOTE_ID=XXXXXXXXXX@c.us
+WWEBJS_TEST_REMOTE_ID=XXXXXXXXXX@c.us
+WWEBJS_TEST_CLIENT_ID=authenticated

.gitattributes

@@ -0,0 +1,4 @@
+* text=auto eol=lf
+
+package-lock.json linguist-generated=true text=auto eol=lf
+docs/* linguist-generated=true text=auto eol=lf

CODE_OF_CONDUCT.md → .github/CODE_OF_CONDUCT.md

@@ -1,4 +1,3 @@
-
 # Contributor Covenant Code of Conduct
 
 ## Our Pledge
@@ -18,23 +17,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
+- Focusing on what is best not just for us as individuals, but for the
   overall community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
+- The use of sexualized language or imagery, and sexual attention or
   advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
   address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -61,7 +60,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-[pedroslopez@me.com](mailto:pedroslopez@me.com).
+[pedroslopez@me.com][email].
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -107,7 +106,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
+standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within
@@ -119,13 +118,14 @@ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
 version 2.0, available at
 [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
 
-Community Impact Guidelines were inspired by 
+Community Impact Guidelines were inspired by
 [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
 
 For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
 at [https://www.contributor-covenant.org/translations][translations].
 
+[email]: mailto:pedroslopez@me.com
 [homepage]: https://www.contributor-covenant.org
 [v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
 [Mozilla CoC]: https://github.com/mozilla/diversity

.github/COMMIT_CONVENTION.md

@@ -0,0 +1,204 @@
+# Git Commit Message Convention
+
+> This is adapted from [Angular's commit convention][angular-commit-convention].
+
+Messages must be matched by the following regex (case-insensitive):
+
+```ts
+/^(revert: )?(feat|fix|docs|style|refactor|perf|test|build|ci|chore|types|infra)(\(.+\))?!?: .{1,72}/i;
+```
+
+The commit type is **case-insensitive** — `feat`, `Feat`, and `FEAT` are all valid.
+
+## Examples
+
+### Features
+
+Appears under "Features" header, message subheader:
+
+```txt
+feat(message): add 'downloadMedia' option
+```
+
+Additional examples:
+
+```txt
+feat(chat): add ability to pin messages
+```
+
+```txt
+feat(contact): add getProfilePicUrl method
+```
+
+### Bug Fixes
+
+Appears under "Bug Fixes" header, client subheader, with a link to issue #28:
+
+```txt
+fix(client): stop client breaking when QR code expires
+
+Closes #28
+```
+
+Additional examples:
+
+```txt
+fix(message): handle media messages without caption correctly
+```
+
+```txt
+fix(auth): resolve authentication timeout on slow connections
+```
+
+### Performance Improvements
+
+Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation:
+
+```txt
+perf(message): remove legacyMode option
+
+BREAKING CHANGE: The legacyMode option has been removed. The new message handling is always used for performance reasons.
+```
+
+Additional example:
+
+```txt
+perf(client): optimize event listener registration
+```
+
+### Documentation
+
+```txt
+docs(readme): update installation instructions
+```
+
+```txt
+docs(api): add examples for message reactions
+```
+
+### Code Refactoring
+
+```txt
+refactor(client): simplify authentication flow
+```
+
+```txt
+refactor(structures): extract common message properties
+```
+
+### Tests
+
+```txt
+test(message): add unit tests for media download
+```
+
+```txt
+test(client): add integration tests for reconnection
+```
+
+### Build System
+
+```txt
+build(deps): update puppeteer to v21.0.0
+```
+
+```txt
+build(webpack): optimize bundle size
+```
+
+### Continuous Integration
+
+```txt
+ci(actions): add automated release workflow
+```
+
+```txt
+ci(tests): run tests on multiple node versions
+```
+
+### Chores
+
+```txt
+chore(gitignore): ignore .vscode directory
+```
+
+```txt
+chore(deps): bump dependencies to latest versions
+```
+
+### Type Definitions
+
+```txt
+types(message): add missing type for MessageMedia
+```
+
+```txt
+types(client): improve ClientOptions interface
+```
+
+### Code Style
+
+```txt
+style(client): fix indentation and spacing
+```
+
+### Reverts
+
+The following commit and commit `667ecc1` do not appear in the changelog if they are under the same release. If not, the revert commit appears under the "Reverts" header:
+
+```txt
+revert: feat(message): add 'downloadMedia' option
+
+This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
+```
+
+A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
+
+```txt
+<type>(<scope>): <subject>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+The **header** is mandatory and the **scope** of the header is optional.
+
+## Revert
+
+If the commit reverts a previous commit, it should begin with `revert:`, followed by the header of the reverted commit. In the body, it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
+
+## Type
+
+If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.
+
+Other prefixes are up to your discretion. Suggested prefixes are `build`, `ci`, `docs`, `style`, `refactor`, and `test` for non-changelog related tasks.
+
+## Scope
+
+The scope could be anything specifying place of the commit change. For example `client`, `message`, `chat`, `contact`, `media`, `auth`, etc...
+
+## Subject
+
+The subject contains succinct description of the change:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize first letter
+- no dot (.) at the end
+
+## Body
+
+Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
+The body should include the motivation for the change and contrast this with previous behavior.
+
+## Footer
+
+The footer should contain any information about **Breaking Changes** and is also the place to
+reference GitHub issues that this commit **Closes**.
+
+**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
+
+A detailed explanation can be found in this [document][commit-message-format].
+
+[angular-commit-convention]: https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular
+[commit-message-format]: https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#

.github/CONTRIBUTING.md

@@ -0,0 +1,43 @@
+# Contributing
+
+If you want to contribute to whatsapp-web.js, start by forking the repository and opening a pull request with your changes. The project uses ESLint and Prettier to enforce a consistent coding style, so setting them up in your development environment is recommended to ensure your contributions meet the formatting standards.
+
+## Questions
+
+Do not open issues for general questions or support requests. For help, please join the [Discord Server][discord] instead. Installation instructions and general guidance are available in the documentation. Issues opened for questions will be closed.
+
+### Issue Tracker
+
+Before creating a new issue, review the existing [issue tracker][issue-tracker] to avoid duplicates.
+
+## Issues and Pull Requests
+
+- **Bug reports** must include a minimal reproduction and clear steps to reproduce the problem.
+- **Feature requests** should clearly describe the use case and explain why the feature belongs in the library.
+- **Pull requests and commit messages** must follow the conventional commit format for both commit messages and the PR title (e.g. `feat(client): add sendMessage option`). The commit type is case-insensitive (`feat`, `Feat`, and `FEAT` are all valid).
+- All pull requests should target the `main` branch unless discussed otherwise.
+- Ensure that linting and tests pass before submitting your pull request.
+
+## Setup
+
+To prepare your development environment:
+
+1. Fork and clone the repository, and ensure you are on the `main` branch.
+2. Run `npm install` to install all dependencies.
+3. Implement your changes or improvements.
+4. Run `npm run check` to execute ESLint and Prettier checks.
+5. Run `npm test` to ensure the test suite passes.
+6. Submit a pull request (make sure it follows the conventional commit format).
+
+## Testing Locally
+
+To test your changes within your own project:
+
+1. Clone the repository and apply your modifications.
+2. Run `npm install` inside the cloned directory.
+3. In your project, run `npm link <path-to-your-clone>` to create a symlink to your local version.
+4. Import the package and verify your changes.
+5. If everything works as expected, you’ve successfully implemented your changes without breaking the library.
+
+[discord]: https://discord.wwebjs.dev/
+[issue-tracker]: https://github.com/wwebjs/whatsapp-web.js/issues

.github/DISCLAIMER.md

@@ -0,0 +1,9 @@
+# Disclaimer
+
+This project is an unofficial library and is not affiliated with, endorsed by, maintained, authorized, or sponsored by WhatsApp Inc., Meta Platforms, or any of their subsidiaries or affiliates. Use of this library and any related components is entirely at your own risk. WhatsApp prohibits the use of unofficial clients, reverse-engineered integrations, automated bots, or other non-official methods of access to its platform, and using this library may violate WhatsApp’s Terms of Service, potentially resulting in temporary or permanent suspension of your WhatsApp account or other enforcement actions. We assume no responsibility or liability if your account is restricted, suspended, or permanently banned, and you are solely responsible for any consequences arising from the use or misuse of this project.
+
+The maintainers and contributors provide this library without any guarantees or warranties, express or implied, regarding its reliability, functionality, or long-term viability. Compatibility with WhatsApp’s private or internal APIs may change at any time without notice, which could cause the library to stop functioning or behave unpredictably. This project has been developed strictly for educational, research, experimental, and hobby purposes and should not be used in commercial, production, or business-critical environments without fully understanding and accepting the associated risks.
+
+For official, secure, and policy-compliant integrations, individuals and businesses are strongly encouraged to use the WhatsApp Business Platform or other authorized APIs provided directly by WhatsApp or Meta. The official WhatsApp website is available at [https://www.whatsapp.com][whatsapp]. "WhatsApp" and all related names, marks, logos, and images are registered trademarks of their respective owners. By using this project, you acknowledge that you understand and accept all of the above terms, limitations, and potential risks, including the possibility of account suspension or banning.
+
+[whatsapp]: https://www.whatsapp.com

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+github: [pedroslopez, PurpShell]
+ko_fi: pedroslopez
+custom: ['paypal.me/psla', 'buymeacoff.ee/pedroslopez']