[roshan-gorasia-cko]

Description

The global error handler reported any error whose file was on a ProcessOut host. Some browsers, such as Chrome on iOS, attribute errors from their own injected scripts to the page URL, so errors that aren't ours were being reported.

Solution

• Only report errors thrown by the processout.js script itself (isProcessOutScriptError in telemetry.ts).
• Skip error events with no error object, which the handler previously dereferenced.
• Version bumped to 1.9.16.

Checklist

• I bumped the version of the project using yarn bump-version
• I have checked the code for any potential issues
• I tested my changes in the browser

Notes

Unit tests cover the filter in test/processout/telemetry.test.ts.

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

The focused changes address the reported telemetry noise with targeted tests and no identified blocking issues.

No open issues 🎉

What changed in this PR

Restricts global error telemetry to processout.js errors on ProcessOut hosts, excluding browser-injected errors attributed to hosted payment pages.

Changes:

• Adds a script URL filter that skips events without an error object.
• Adds targeted filter tests and a telemetry test loader.
• Bumps the version to 1.9.16.

File	Description
test/​support/​loadNamespace.ts	Adds a telemetry namespace loader for tests.
test/​processout/​telemetry.test.ts	Tests accepted URLs and rejected error events.
src/​processout/​telemetry.ts	Defines the script error filter.
src/​processout/​processout.ts	Applies the filter to global error reporting.
package.json	Bumps the version to 1.9.16.

_{Review effort: Balanced}