Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@sentry/browser - 'defaultIntegrations' does not exist, did you mean 'getDefaultIntegrations'? #10353

Closed
luc122c opened this issue Jun 11, 2024 · 2 comments · Fixed by #10355
Closed
Assignees
Labels
Type: Content Issues about the contents of our docs

Comments

@luc122c
Copy link

luc122c commented Jun 11, 2024

Core or SDK?

Platform/SDK

Which part? Which one?

https://docs.sentry.io/platforms/javascript/best-practices/multiple-sentry-instances/

Description

I'm following the guidance and examples for multiple Sentry instances. In the example, defaultIntegrations is imported from @sentry/browser, however my IDE complains:

Property 'defaultIntegrations' does not exist on type 'typeof import("[...]/@sentry/browser/types/index")'. Did you mean 'getDefaultIntegrations'?

Indeed, when looking at the exports for @sentry/[email protected], the only similar export is getDefaultIntegrations from ./sdk.

Suggested Solution

Please update the documentation to reflect the exports.

@luc122c luc122c added the Type: Content Issues about the contents of our docs label Jun 11, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Jun 11, 2024

Assigning to @getsentry/support for routing ⏲️

@AbhiPrasad
Copy link
Member

fixed with #10355

@AbhiPrasad AbhiPrasad linked a pull request Jun 11, 2024 that will close this issue
6 tasks
@AbhiPrasad AbhiPrasad self-assigned this Jun 11, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Content Issues about the contents of our docs
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants