Skip to content

Support for chrome lowend browser #16069

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
midhunem42 opened this issue Apr 15, 2025 · 2 comments
Closed

Support for chrome lowend browser #16069

midhunem42 opened this issue Apr 15, 2025 · 2 comments

Comments

@midhunem42
Copy link

midhunem42 commented Apr 15, 2025

Low-End Browser Compatibility Issue with @sentry/react (ESM Output)
Context:

We are integrating @sentry/react into our web application for error monitoring. The current version of @sentry/react outputs an ECMAScript Module (ESM) build by default.

Issue:
Low-end or legacy browsers (such as Internet Explorer 11 or older chrome browser) do not support ESM. As a result, our application fails to load or throws runtime errors when accessed from such browsers.

Root Cause:

The ESM output from @sentry/react uses modern JavaScript syntax (e.g., import/export, arrow functions, etc.).

These syntax features are not transpiled or polyfilled in ESM builds, leading to immediate syntax errors in unsupported browsers.

Browsers without ESM support cannot parse or execute ESM scripts, and fallback to no script loading.

Impact:

  • Application crashes or fails to load for users on unsupported browsers.
  • Potential loss of monitoring for those sessions, defeating the purpose of error reporting.
  • Degraded user experience on older or constrained devices.

Solution Brainstorm

Use a Legacy-Compatible Build (if available)

  1. Goal: Use a CommonJS (CJS) or UMD version of Sentry instead of the ESM version.

Are there any alternative methods to support low-end browsers?

Product Area

Other

@getsantry
Copy link

getsantry bot commented Apr 15, 2025

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Apr 15, 2025
@AbhiPrasad AbhiPrasad transferred this issue from getsentry/sentry Apr 15, 2025
@AbhiPrasad
Copy link
Member

Hey @midhunem42 thanks for opening an issue.

We are not going to support older browsers with our default CDN bundle or npm package. We recommend bundling and polyfilling the SDK code to support older browser versions via tooling like babel.

You can use something like https://github.com/browserslist/browserslist to configure what browsers you want to support, which will be picked up by babel. This should be supported by bundlers like webpack, rollup, and vite.

@AbhiPrasad AbhiPrasad closed this as not planned Won't fix, can't repro, duplicate, stale Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants