-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Undocumented Limitation of Lazy-Loading SDK #4722
Comments
Routing to @getsentry/{"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/teams#get-a-team-by-name"} for triage. ⏲️ |
Gah - that fix was was linked to the wrong issue. Sorry, folks. Reopening. |
When we made the changes in #4204 (to export `BrowserTracing` directly rather than as part of `Sentry.Integrations`), we didn't make the change in the tracing CDN bundle. While It's true that there's no bundle size issue there (mongo and friends never were getting included in the CDN bundle, so there was nothing to fix), it did mean that when we changed the docs to match the above PR's changes, we ended up breaking CDN folks' usage of `BrowserTracing`. This fixes that by making the same change in the tracing CDN bundle as was made for the npm package. Fixes getsentry/sentry-docs#4722.
I'm pushing a fix now - thanks for pointing this out! |
Core or SDK?
Platform/SDK
Which part? Which one?
Javascript
Description
I recently added version for release health / sessions to my JS SDK, but was only seeing sessions with errors. I ended up tracing this back to use of the lazy-loading script. Since it will only initialize the SDK if there is an error / exception, 100% of reported sessions were 'crashes'.
Suggested Solution
I believe this should be added as a note under the Limitations section of the Lazy Loading docs -
https://docs.sentry.io/platforms/javascript/install/lazy-load-sentry/#limitations
This was when searching the docs for "sessions" there is a better chance of discovering why this behavior is happening.
The text was updated successfully, but these errors were encountered: