This new top-level config allows to opt-out of any added integration, ensuring it is not actually added.

This is mainly designed to opt-out of default integrations, but will also apply to any manually added integration.

There are type hints that should help with usage there, but any key is allowed to keep this flexible. Type hints are manually configured (could not find a way to infer this from integrations, as the names are not statically exposed there...) for now.

image

Usage:

Sentry.init({
 disableIntegrations: { BrowserSession: true, InboundFilters: false }
});

Will disable the browserSessionIntegration but not the inboundFilters one.

Syntax

The linked issue proposed to allow to pass { IntegrationName: false } to defaultIntegrations. While this is a nice API from a users POV, it is trickier than I imagined - the problem is the logic we have around defaultIntergations. E.g. the browser SDK will basically do this:

function init(options) {
 const opts = {
 defaultInterhations: options.defaultIntergations || getDefaultIntergations()
 // ...
 };
}

Which makes it much trickier to handle these things and would require bigger changes in various places 😬 So this PR tries a different approach, by having a new config property for this 🤔 If there are other ideas/thoughts around this, happy to hear them!

Closes #14950