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

Change Sentry init to avoid polluting global scope #982

Open
noeldevelops opened this issue Jan 28, 2025 · 0 comments
Open

Change Sentry init to avoid polluting global scope #982

noeldevelops opened this issue Jan 28, 2025 · 0 comments
Assignees

Comments

@noeldevelops
Copy link
Member

While "rubber ducking" about Sentry 3rd party errors showing up as a team, we (re?)discovered that Sentry recommends we initialize our client in a custom way. Let's do it!

See Node client example here: https://github.com/getsentry/sentry-javascript/blob/a27652f09538e91d3c6c23f8eeadb75743067428/packages/node/src/sdk/index.ts#L104

Might need some discussion and further investigation to make sure we continue to catch all Unhandled exceptions with Sentry 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants