Regression: @sentry/astro stopped re-exporting captureException in 8.8.0

[arty-name]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Self-hosted/on-premise

Which SDK are you using?

@sentry/astro

SDK Version

8.8.0

Framework Version

4.10.0

Link to Sentry event

No response

SDK Setup

  integrations: [
    sentry({
      enabled: { client: false, server: true },
      tracePropagationTargets: [],
    }),
  ],

Steps to Reproduce

1. Upgraded the SDK to the latest version to address Node SDK generating Error: ENOENT: no such file or directory #12059 and Astro integration follow the guide will get a error ENOENT: no such file or directory, open '/Users/xxx/astro-project/node_modules/@sentry/astro/esm/@sentry/node' #12192
2. Tried accessing captureException in different ways:

import { captureException } from '@sentry/astro';
import * as Sentry from '@sentry/astro';
(await import('@sentry/astro')).captureException;

Expected Result

captureException should be available and usable, since the TypeScript types for the SDK mark it as present

Actual Result

Logging Sentry.captureException prints undefined, the property is absent from Sentry, seems not to be properly re-exported, while many other members of Sentry are present. I can access captureException when importing it directly from @sentry/node.

[Lms24]

Hey @arty-name to narrow this down - does this occur on the server or client side?

[arty-name]

This was on the server side

[Lms24]

I could reproduce this locally, so I opened #12453 to fix it. Thanks for reporting! This is gonna be included in the release after 8.9.0.

[Lms24]

This was released with version 8.9.1 - feel free to give it a try and let me know if the issue is fixed.

[arty-name]

Thank you for the very quick processing of this issue! I confirm that it has been resolved 👍