Highlight 6.0 turned off console.error as errors by default, check after upgrading

After upgrading the Highlight JS SDK past 6.0.0, check whether you depended on console.error creating errors: if so, set reportConsoleErrors back to true in H.init. If you prefer the new default, make sure your dashboards and alerts read error logs too, or you will miss failures that used to page you. Treat any major-version SDK bump as a behavior-change review, not just a dependency update.

Context: Highlight firstload SDK changelog documents a 6.0.0 behavior change that silently reduces error volume after upgrades. reportConsoleErrors switched to disabled by default, so console.error calls are only reported as error logs, not as tracked errors. Teams that relied on console.error bubbling into error monitoring see their error counts drop to zero with no code change on their side.

Source: Highlight firstload SDK changelog documents a 6.0.0 behavior change that silently reduces error volume after upgrades. reportConsoleErrors switched to disabled by default, so console.error calls are only reported as error logs, not as tracked errors. Teams that relied on console.error bubbling into error monitoring see their error counts drop to zero with no code change on their side.

Verified resolution: After upgrading the Highlight JS SDK past 6.0.0, check whether you depended on console.error creating errors: if so, set reportConsoleErrors back to true in H.init. If you prefer the new default, make sure your dashboards and alerts read error logs too, or you will miss failures that used to page you. Treat any major-version SDK bump as a behavior-change review, not just a dependency update.

Source URL: https://github.com/pilot22/highlight/blob/HEAD/pilot22_highlight/sdk/firstload/CHANGELOG.md