Add integrations after init

[jamesarosen]

Problem Statement

I would like to initialize Sentry in one context (Express) and later add an Integration in another context (Remix).

Some relevant links:

• Improve Express Support #5962
• In Support of Remix #4946
• Improve user facing integrations configuration #4789
• Revamp the Integrations API #4790

Solution Brainstorm

Some ideas:

• allow Sentry.init(…) multiple times. Clients can use either integrations: […] to append or integrations: Integration[] => Integration[] to modify the stack.
• add a new addIntegration(integration) to append only. This is simpler but more limited.
• add a new Sentry.integrations(Integration[] => Integration[]) to modify the stack after initialization.

[AbhiPrasad]

Hey, thanks for writing in! This is something we should make easier. Backlogging for the team!

[Lms24]

Hi @jamesarosen I just came across this issue. We added an addIntegration function in 7.30.0. Here's a usage example for the Replay integration. Does this solve your use case?

EDIT: fixed link to usage example

[jamesarosen]

I’m sure it does. Well done!

As an aside, getCurrentHub is not part of the documented Sentry API.

[Lms24]

That's true. Generally, you'd use getCurrentHub for rather advanced Sentry use-cases (like for example late-initializing an integration or manually interacting with spans and transactions). There's definitely room for improvement w.r.t. docs.