Context
With the addition of @microsoft/api-extractor in #6093, we now have visibility into the public API surface. The tool reports 36 ae-forgotten-export warnings — types that appear in public function signatures but are not exported from index.ts.
None of these types are documented in the Sentry docs, and no users have reported needing them. TypeScript's structural typing means consumers can pass plain object literals without importing the types explicitly.
What needs reviewing
For each type, decide whether to export it (make it part of the public API) or mark it @internal (explicitly keep it private).
Options/config types (used as integration/function parameters)
ReactNativeTracingOptions, ReactNativeTracingState, ReactNativeTracingIntegrationReactNavigationIntegrationOptions, ReactNativeNavigationOptionsReactNativeClientOptions, ReactNativeTransportOptions, BaseReactNativeOptions, ReactNativeWrapperOptionsReactNativeErrorHandlersOptions, LinkedErrorsOptions, BreadcrumbsOptionsMobileReplayOptions, MobileReplayIntegrationHermesProfilingOptionsGraphQLReactNativeIntegrationOptions, SpotlightReactNativeIntegrationOptions, SupabaseReactNativeIntegrationOptionsFeedbackFormProps, FeedbackButtonProps, ScreenshotButtonProps, FeedbackFormThemeTouchEventBoundaryPropsAppStartIntegration, defaultIdleOptions
Internal/external types (likely should stay unexported)
FeedbackFormState, FeedbackIntegration, GlobalErrorBoundaryState — internal component stateReplay, ReplayConfiguration — @sentry/browser internalsHostComponent, ViewProps — react-native typesExpoAssetInstance, ExpoImageSource, ExpoImageLoadOptions, ExpoImageRef — internal Expo types
Additional items to review
logger from @sentry/browser is exported publicly — is this intentional?
Context
With the addition of
@microsoft/api-extractorin #6093, we now have visibility into the public API surface. The tool reports 36ae-forgotten-exportwarnings — types that appear in public function signatures but are not exported fromindex.ts.None of these types are documented in the Sentry docs, and no users have reported needing them. TypeScript's structural typing means consumers can pass plain object literals without importing the types explicitly.
What needs reviewing
For each type, decide whether to export it (make it part of the public API) or mark it
@internal(explicitly keep it private).Options/config types (used as integration/function parameters)
ReactNativeTracingOptions,ReactNativeTracingState,ReactNativeTracingIntegrationReactNavigationIntegrationOptions,ReactNativeNavigationOptionsReactNativeClientOptions,ReactNativeTransportOptions,BaseReactNativeOptions,ReactNativeWrapperOptionsReactNativeErrorHandlersOptions,LinkedErrorsOptions,BreadcrumbsOptionsMobileReplayOptions,MobileReplayIntegrationHermesProfilingOptionsGraphQLReactNativeIntegrationOptions,SpotlightReactNativeIntegrationOptions,SupabaseReactNativeIntegrationOptionsFeedbackFormProps,FeedbackButtonProps,ScreenshotButtonProps,FeedbackFormThemeTouchEventBoundaryPropsAppStartIntegration,defaultIdleOptionsInternal/external types (likely should stay unexported)
FeedbackFormState,FeedbackIntegration,GlobalErrorBoundaryState— internal component stateReplay,ReplayConfiguration—@sentry/browserinternalsHostComponent,ViewProps— react-native typesExpoAssetInstance,ExpoImageSource,ExpoImageLoadOptions,ExpoImageRef— internal Expo typesAdditional items to review
loggerfrom@sentry/browseris exported publicly — is this intentional?