initWithoutDefaultIntegrations and getDefaultIntegrationsWithoutPerformance methods for @sentry/bun

[Thanaen]

Problem Statement

@sentry/node calls the “initWithoutDefaultIntegrations” method combined with “getDefaultIntegrationsWithoutPerformance” to initialize Sentry in “error handling” mode only.

It would appear that the @sentry/bun package does not expose these methods, but @sentry/bun users would also benefit from them.

Would it be possible to add them?

An alternative solution would be to use @sentry/node with bun, but I'm not sure about the side effects.

Thanks!

Solution Brainstorm

Add “initWithoutDefaultIntegrations” and “getDefaultIntegrationsWithoutPerformance” methods to @sentry/bun

[Thanaen]

(The purpose of this feature would be to reduce Sentry's impact on bun performance, as mentioned in this issue: #12561)

[chargome]

Hi @Thanaen, thanks for reaching out. You could just filter the integrations based on your needs like this:

Sentry.init({
  // ...
  integrations: function (integrations) {
    // integrations will be all default integrations
    return integrations.filter(function (integration) {
      return integration.name !== "Breadcrumbs";
    });
  },
});

docs here

[Thanaen]

This could be a good workaround, even if it's less simple to use than the methods provided for Node.js!

Does it allow tree-shaking of disabled integrations?

[chargome]

@Thanaen yes this should be tree-shakable unfortunately this would not be treeshakable. You would need to provide your own client instead, similar to https://docs.sentry.io/platforms/javascript/configuration/tree-shaking/#tree-shaking-default-integrations. In your case this would be a BunClient though. Sorry for the confusion!

[Thanaen]

Ok!

This means that Sentry users who use Bun should maintain a list of integrations to disable if they don't want to use tracing and performance analysis, it's not ideal, but I can live with it for now

[chargome]

@Thanaen updated my comment above!

[Thanaen]

Thanks for the update!