fix: use beacon api check removed

[seeratawan01]

PR Type

Bug fix

---

Description

• Simplified the condition for enabling the beacon API by removing the check for options.use_beacon_api and directly checking for navigator.sendBeacon.
• This change ensures that the beacon API is used whenever it is available, potentially fixing issues where it was not used due to the removed condition.

---

Changes walkthrough 📝

	Relevant files
Bug fix	usermaven.ts Simplify beacon API usage check in UsermavenClientImpl      packages/javascript-sdk/src/usermaven.ts Removed the check for options.use_beacon_api before using navigator.sendBeacon. Simplified the condition to only check if navigator.sendBeacon is available. +1/-1

---

💡 PR-Agent usage: Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions[bot]]

PR Reviewer Guide 🔍

🏅 Score: 85

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review Possible Bug Removing the `options.use_beacon_api` check might cause unintended behavior if there are scenarios where the beacon API should not be used even if available. This change assumes that `navigator.sendBeacon` being available is the only condition needed to enable the beacon API, which might not align with user configurations or preferences.

Code feedback:

---

relevant file	packages/javascript-sdk/src/usermaven.ts
suggestion	Consider reintroducing a configurable option to enable or disable the beacon API, allowing users to opt-out if necessary. This can be achieved by adding a new option in the configuration and checking it along with `navigator.sendBeacon`. This approach provides flexibility and respects user preferences, especially in environments where beacon usage might need to be controlled. [important]
relevant line	if (navigator?.sendBeacon) {

---

[github-actions[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Enhancement	Add error handling for unsupported Beacon API ___ **Consider adding a fallback or an error handling mechanism for browsers that do not support the Beacon API. This ensures that the functionality dependent on this.beaconApi does not break in such environments.** [packages/javascript-sdk/src/usermaven.ts [975-977]](https://github.com/usermaven/usermaven-js/pull/95/files#diff-a9e765a7bfd2dfbeba110d6b5d12e58d21090506ae52b206581809fae414ebfeR975-R977) ```diff if (navigator?.sendBeacon) { this.beaconApi = true; +} else { + console.error("Beacon API is not supported in this browser."); + this.beaconApi = false; } ``` Suggestion importance[1-10]: 8 Why: The suggestion to add error handling for unsupported Beacon API is valid and enhances the robustness of the code by ensuring that functionality does not break in environments where the Beacon API is not supported.	8