From 11c6b39491040a9b00f6fdd022d90215d2346fd7 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 30 Apr 2026 15:21:54 +0000 Subject: [PATCH 1/4] docs(deno): Add Deno-specific Sentry import example for Supabase integration The Supabase integration page's configuration snippet did not show the Sentry import statement. For Deno users, the import syntax is unique (npm: prefix) and must come before other imports for correct instrumentation. Add a PlatformSection with a Deno-specific example showing the correct import order. Also fix minor typo in the configuration section intro sentence. Co-Authored-By: Claude Co-authored-by: Sergiy Dybskiy --- .../configuration/integrations/supabase.mdx | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx index 9a1f27ff24107..b692da9d745d0 100644 --- a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx @@ -39,7 +39,9 @@ You need to have both the Sentry SDK and the Supabase library installed. For Sup ## Configuration -This is the preferred method for most use cases. and follows Sentry's standard integration pattern. +This is the preferred method for most use cases and follows Sentry's standard integration pattern. + + ```javascript import { createClient } from '@supabase/supabase-js'; @@ -55,6 +57,29 @@ Sentry.init({ }); ``` + + + + +In Deno, import the Sentry SDK from the npm registry **before** any other imports to ensure it can instrument your application correctly: + +```javascript +import * as Sentry from 'npm:@sentry/deno'; +import { createClient } from 'npm:@supabase/supabase-js'; + +const supabaseClient = createClient('YOUR_SUPABASE_URL', 'YOUR_SUPABASE_KEY'); + +Sentry.init({ + dsn: 'YOUR_DSN', + integrations: [ + Sentry.supabaseIntegration({ supabaseClient }) + ], + tracesSampleRate: 1.0, +}); +``` + + + ## Generated Spans The integration provides comprehensive monitoring for both authentication and database operations: From 9c0689c4c7cf5c084fdbd4b74d293cfbdfa1ea72 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 30 Apr 2026 15:28:09 +0000 Subject: [PATCH 2/4] docs(supabase): Use dynamic SDK import placeholder for Sentry\n\nAdd to non-Deno config so pulls the correct SDK per platform. Keep Deno-specific import and ensure it appears before other imports.\n\nRefs DOCS-ANT\nCo-Authored-By: Claude Co-authored-by: Sergiy Dybskiy --- .../javascript/common/configuration/integrations/supabase.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx index b692da9d745d0..779e30ab24fdc 100644 --- a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx @@ -44,6 +44,7 @@ This is the preferred method for most use cases and follows Sentry's standard in ```javascript +import * as Sentry from "___SDK_PACKAGE___"; import { createClient } from '@supabase/supabase-js'; const supabaseClient = createClient('YOUR_SUPABASE_URL', 'YOUR_SUPABASE_KEY'); From f46dc0009101b62a8286dba1122610bc66171735 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 7 May 2026 16:29:11 +0000 Subject: [PATCH 3/4] docs(supabase): De-duplicate config by splitting imports per platform\n\nUse platform-specific blocks only for import lines (Deno vs non-Deno) and keep a single shared initialization snippet to avoid divergence. Add a Deno note about import order.\n\nRefs DOCS-ANT\nCo-Authored-By: Claude Co-authored-by: Sergiy Dybskiy --- .../configuration/integrations/supabase.mdx | 33 +++++++++---------- 1 file changed, 16 insertions(+), 17 deletions(-) diff --git a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx index 779e30ab24fdc..001a1fb39792a 100644 --- a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx @@ -41,33 +41,30 @@ You need to have both the Sentry SDK and the Supabase library installed. For Sup This is the preferred method for most use cases and follows Sentry's standard integration pattern. +### Imports + + + +```javascript +// Import Sentry from npm and ensure it appears before other imports +import * as Sentry from 'npm:@sentry/deno'; +import { createClient } from 'npm:@supabase/supabase-js'; +``` + + + ```javascript import * as Sentry from "___SDK_PACKAGE___"; import { createClient } from '@supabase/supabase-js'; - -const supabaseClient = createClient('YOUR_SUPABASE_URL', 'YOUR_SUPABASE_KEY'); - -Sentry.init({ - dsn: 'YOUR_DSN', - integrations: [ - Sentry.supabaseIntegration({ supabaseClient }) - ], - tracesSampleRate: 1.0, -}); ``` - - -In Deno, import the Sentry SDK from the npm registry **before** any other imports to ensure it can instrument your application correctly: +### Initialize ```javascript -import * as Sentry from 'npm:@sentry/deno'; -import { createClient } from 'npm:@supabase/supabase-js'; - const supabaseClient = createClient('YOUR_SUPABASE_URL', 'YOUR_SUPABASE_KEY'); Sentry.init({ @@ -79,7 +76,9 @@ Sentry.init({ }); ``` - + +For Deno, always place the `npm:@sentry/deno` import before other imports so instrumentation can attach correctly. + ## Generated Spans From c61d4d2f14b00c5f4e9f260a657801855b82e1bb Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 7 May 2026 16:32:57 +0000 Subject: [PATCH 4/4] docs(supabase): Remove unguarded Deno-only note\n\nNote was redundant (imports already first in snippets) and showed for all platforms.\n\nRefs DOCS-ANT\nCo-Authored-By: Claude Co-authored-by: Sergiy Dybskiy --- .../javascript/common/configuration/integrations/supabase.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx index 001a1fb39792a..d66a4ec606fda 100644 --- a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx @@ -76,10 +76,6 @@ Sentry.init({ }); ``` - -For Deno, always place the `npm:@sentry/deno` import before other imports so instrumentation can attach correctly. - - ## Generated Spans The integration provides comprehensive monitoring for both authentication and database operations: