Module '"@sentry/nextjs"' has no exported member 'CaptureContext' and no exported member '"ExclusiveEventHintOrCaptureContext"'.

[RoyBkker]

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?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

10.30.0

Framework Version

15.5.9

Link to Sentry event

No response

Reproduction Example/SDK Setup

import type { CaptureContext, ExclusiveEventHintOrCaptureContext } from "@sentry/nextjs";
import { captureException, captureMessage, flush, type SeverityLevel } from "@sentry/nextjs";

export async function captureExceptionAndFlush(
  error: unknown,
  context?: ExclusiveEventHintOrCaptureContext,
  timeout = 2000
): Promise<void> {
  captureException(error, context);
  await flush(timeout);
}

export async function captureMessageAndFlush(
  message: string,
  captureContext?: CaptureContext | SeverityLevel,
  timeout = 2000
): Promise<void> {
  captureMessage(message, captureContext);
  await flush(timeout);
}

Steps to Reproduce

See the Typescript errors when importing.

Module '"@sentry/nextjs"' has no exported member 'ExclusiveEventHintOrCaptureContext'.ts(2305)
Module '"@sentry/nextjs"' has no exported member 'CaptureContext'.ts(2305)

Expected Result

Can import the Types

Actual Result

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1303

[chargome]

Hey @RoyBkker thanks for reaching out!

You're right that we do not export these types atm.

Would something like :

// infer parameter type 
type CaptureExceptionContext = Parameters<typeof captureException>[1];

also work fo you?

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #18509, which was included in the 10.31.0 release.