PerformanceResourceTiming.nextHopProtocol is used without check for support

[Mantish]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Self-hosted/on-premise

Which SDK are you using?

@sentry/browser

SDK Version

9.34.0

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

We're updating our Sentry dependencies from v8 to v9, but Sentry performance monitoring (tracing integration) causes a breaking error in devices that use older browsers.

Looking at the error data, we can trace the error to the usage of nextHopProtocol without check for support. I can see that this code was added in #15161

Steps to Reproduce

Just loading any page and initializing Sentry triggers this error.

Expected Result

Sentry should initialize without issues, even in older browsers that don't have full support of browser APIs

Actual Result

Sentry triggers an error that breaks the whole application

[AbhiPrasad]

Hey @Mantish thanks for writing in.

What browser/browser version are you testing this on? Here are the supported browser versions by the Sentry SDK in v9: https://docs.sentry.io/platforms/javascript/troubleshooting/supported-browsers/

Sentry's latest JavaScript SDKs require ES2020 compatibility. The minimum supported browser versions are:

• Chrome 80
• Edge 80
• Safari 14, iOS Safari 14.4
• Firefox 74
• Opera 67
• Samsung Internet 13.0

[Mantish]

yeah, we need to support much older browsers so we transpile all our dependencies, which has been working fine for the most part.
For what I can see this is the only issue that breaks our Sentry integration

[AbhiPrasad]

yeah fair, I think we can add a guard for this so that we unblock you.