Investigate pluggable integrations

[mydea]

Description

We have a list of non-default integrations in the SDKs. We should take some time to review all of them, and check the following things:

• What does the integration actually do?
• Is this valuable? Do we (still) need this?
• Should this possibly become a default integration?
• Or else, should this possibly remain pluggable, but recommended in onboarding?
• Or do we possibly want to remove this in the future because we do not think we need it anymore?

Pluggable integrations from core

• captureConsoleIntegration
• extraErrorDataIntegration
• metadataIntegration
• zodErrorsIntegration

Pluggable integrations from browser

• contextLinesIntegration
• httpClientIntegration
• reportingObserverIntegration

[dirstart]

I have the same opinion as you.
I also noticed that besides the official repos on GitHub, there aren't any third-party integrations.
I'm looking to build a plugin for white screen detection—should I just go ahead and submit a pull request to the official repo?

[Lms24]

Hey @dirstart 👋 There are some 3rd party SDK integrations for Sentry (that we know of), like for example supabase that live in their own repos. This is perfectly fine for us!

If you want to write an integration for the Sentry SDK, feel free to start out with doing it in your own repo (and npm package). If you then want to contribute the integration to the Sentry repo, feel free to open an issue about it but we can't make guarantees, as this has implications on our support capacities.

[lforst]

We decided to just remove the debugIntegration and sessionTimingIntegration for v9 so I removed them from this list.

[mydea]

@lforst I think we can close this? We decided to deprecate two of the integrations, i guess we'll leave the rest as is (for now)?

[lforst]

@mydea I think so!

FTR: We deprecated the debug and session timing integrations. The ones outlined in this issue still make sense.