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

Supabase Support #15436

Open
smeubank opened this issue Feb 18, 2025 · 2 comments · May be fixed by #15719
Open

Supabase Support #15436

smeubank opened this issue Feb 18, 2025 · 2 comments · May be fixed by #15719
Assignees

Comments

@smeubank
Copy link
Member

Problem Statement

Sentry's Node.js SDK does not have OOTB support for Supabase features. Supabase is famously a new service for your postgres DB, but it does much more today.

in order of what the SDK should support, and can be broken into independently shippable features:

For Node in particular there are a number of ways documented by Supabase to interact with their Postgres DBs, Let's ensure we can support as many as possible

Image

Solution Brainstorm

There is a 3rd party integration for their Node.js library, for reference.

This introduces a requirement to install yet another library, the user should only need the Sentry SDK and Supbase client, or other relevant client for builing

@cobyeastwood183
Copy link

hey, got a ticket on supporting this, https://sentry.zendesk.com/agent/tickets/146070

@smeubank
Copy link
Member Author

hey, got a ticket on supporting this, https://sentry.zendesk.com/agent/tickets/146070

this was actually a mixup, the dev is using edge functions and should use the Sentry Deno SDK directly. But this was further confusion caused by there being another package floating around out there

@lforst lforst linked a pull request Mar 20, 2025 that will close this issue
@smeubank smeubank linked a pull request Mar 20, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

3 participants