No fetch calls on Edge 16/17/18 or iOS10 after transpiling to esmodules

[jasonfry]

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 package are you using?

@sentry/react

SDK Version

7.7.0

Framework Version

No response

Link to Sentry event

No response

Steps to Reproduce

1. When upgrading to v7 and above, Edge 16/17/18 and iOS 10 safari would no longer load our pages.
2. So I set webpack to include @sentry packages via exclude: /node_modules\/(?!(@sentry)\/).*/, (we normally exclude node_modules). Our @babel/present-env target is targets: { esmodules: true },
3. After this new build, those browsers started loading our pages okay.
4. When I view the response to captureMessage it appears to work fine, I get an event_id returned.

Expected Result

I expect the network calls to be made to register these event_id's on all browsers

Actual Result

No network request is made in Edge 16/17/18 or iOS 10 Safari, so these events never get to Sentry.

In more modern browsers I do get the network requests and they work as normal in Sentry.

---

Internal tracking:

• Add option to nextjs SDK (fix(nextjs): Add transpileClientSDK option #5472)
• Document nextjs option and document necessary build pipeline changes for non-nextjs people (feat(nextjs): Add transpileClientSDK option and build config page sentry-docs#5350)

[Noitidart]

Same situation here. On iOS 10 Safari, v7+ is not working. I'm using Next.js. With Sentry v7 installed, all my other JS is broken too. Mine is not self-hosted though, it's using Sentry. A discussion topic is open here on Sentry v7 breaking entire JS system in Next.js - vercel/next.js#38935

[Lms24]

Hi @jasonfry and @Noitidart, thanks for writing in. We switched to ES6 by default with v7 of the JS SDK. So if you want to support browsers that don't support ES6, you need to downcompile the SDK to es5 yourself (e.g. with Babel). An alternative solution is to use our es5 CDN bundles.

Hope this helps!

[Noitidart]

Thanks @Lms24 can you show us how to do that. As I use Vercel/Next.js because it's batteries included, no messing around with build systems. Sentry integrates with Vercel/Next.js - it used to work fine - but is now breaking their batteries included design.

[jasonfry]

Hey @Lms24 thanks for the speedy reply!

I thought it should work on iOS10 and Edge 15-18 as they are marked as okay on https://caniuse.com/?search=es6 so therefore should work even without transpiling? I guess my issue as noted above is a step too far for the real question, I only tried transpiling as it wasn't working in these browsers, so @Noitidart's reply is more on-point.

So should these browsers be working with Sentry v7 as they support ES6?

[Lms24]

@Noitidart

This might help you out for Next.JS: https://www.npmjs.com/package/next-transpile-modules

@jasonfry thanks for clarifying. Right, if these browsers support es6 fully, then there shouldn't be a problem with v7. Would be interesting to know what's going on here. Do you have more details (e.g. error messages, stack traces) on the errors you got when using the untranspiled version?

[lobsterkatie]

Hi, all.

I'm pretty sure I know the culprit here. We use object spread syntax in the SDK, which none of those browsers support.

As far as fixing it goes, a) I tried the package Lukas linked, and it doesn't seem to work, but b) I hacked together something which seems to, and we're going to discuss tomorrow in our standup whether we want to include it in the SDK or just document it as a workaround.

I'll update once we've made a decision.

[Noitidart]

Major <3 guys thanks for helping work this and testing each others ideas! And thanks @jasonfry for getting this conversation started! I was hesitant to start it, not good with words here lol.

It's awesome to hear you tested that package and it didn't work. I was hesitant to use that package too as (next-transpile-modules), it seems the maintenance is a bit uncertain, there's a fork of it, and then many open issues.