Skip to content

ref(sourcemaps): added faulty community-maintained packages to troubleshooting doc #12915

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Apr 24, 2025
Merged

ref(sourcemaps): added faulty community-maintained packages to troubleshooting doc #12915

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e7d5d1f
ref(sourcemaps): added fault integration to troubleshooting doc
doronpr Mar 4, 2025
d0adecd
Update platform-includes/sourcemaps/troubleshooting/javascript.mdx
Lms24 Apr 24, 2025
93cc616
add conflicting package by name
lforst Apr 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions platform-includes/sourcemaps/troubleshooting/javascript.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,3 +184,11 @@ The Sentry Node.js SDK generally works well with the [source-map-support](https:

If you are uploading source maps to Sentry or if you are using a Sentry SDK in the browser, your code cannot use the `source-map-support` package.
`source-map-support` overwrites the captured stack trace in a way that prevents our source map processors from correctly parsing it.

### Third-Party Integrations

In rare cases, faulty or outdated third-party integrations may modify the error sent to Sentry, causing essential information to be lost and preventing Sentry from displaying the source map. If you're using a third party integration or other community-maintained packages, try to temporarily disable them to rule out this possibility.

We will collect known instances of conflicting third-party packages here:

- `posthog-js` versions from `1.207.4` to `1.229.0` (fixed in `posthog-js` version `1.229.1`)
Loading