feat(client): move sendReaction method to the Client

[maxkoryukov]

PR Details

Message.react moved to Client.sendReaction (and the old Message.react now calls
`this.client.sendReaction)

Description

The new method created from Message.react, and the original method now calls the new one.

Motivation and Context

With this method it is possible to send reactions to any message, not only to the just received message, or fetched by "load/fetch messages"

How Has This Been Tested

Basically, the code were just moved, so I called both:

• msg.react
• client.sendReaction

and both worked in private/group messages.

Environment

I've tested with whatsapp-web.js@1.34.6 inside a node:24.12.0-alpine3.23 (linux) docker image.

webVersion: "2.3000.1036705643"

Types of changes

• Dependency change
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the style guidelines of this project.
• All new and existing tests pass (npm test).
• Typings (e.g. index.d.ts) have been updated if necessary.
• Usage examples (e.g. example.js) / documentation have been updated if applicable.

Related PRs

• replaces feat(client): add sendReaction method to the Client #4004

[BenyFilho]

Check Lint errors

Lint Errors

[maxkoryukov]

Check Lint errors

I've fixed it.

And today I also will run jsdoc to add sendReaction to the documentation

[maxkoryukov]

guys, i ran jsdoc , because i've added a new method on the Client class, but it seems like the documentation wasn't updated for a while, and there are too many changes to include them all into this PR

so i split them:

• this PR (#210695) - updates in the JS code
• another PR (docs: update jsdoc documentation (for v1.34.6) #201700) - updates for the documentation

but the obviously - the "doc PR" contains all changes from "js PR"

[Adi1231234]

Nice work!

[maxkoryukov]

guys, is there something that prevents this PR from being merged? do i need to fix something else, or it is just waiting for the "merge time"?

[BenyFilho]

guys, is there something that prevents this PR from being merged? do i need to fix something else, or is it just waiting for the "merge time"?

Update the branch

[BenyFilho]

@maxkoryukov, please, always check your PRs. To be merged, the branch needs to be updated

[maxkoryukov]

I think branches were updated, but anyway I rebased this PR's branch on top of the main, so now the branches should be ok