supabase / supabase / 42667484518

87%

Build Type

push

github

Committed by web-flow

Commit Message

fix(studio): apply Studio error policy on the TanStack server (#53174)

Part of FE-4772. Follow-up to #53059.

## Problem

#53059 made `beforeSend` drop `UserSqlError` and redact
`StudioSqlError`, and added that hook to `sentry.server.config.ts`. Only
the Next build loads that file. Production runs the TanStack Start
build, which initializes server Sentry in `instrument.server.mjs` with
no `beforeSend`.

## Solution

- **`buildSentryServerOptions`** (`lib/sentry-server-options.ts`) holds
the shared server options: DSN, environment, trace sample rate,
`ignoreErrors`, and `beforeSend` calling `applyStudioErrorPolicy`. It
mirrors `buildSentryClientOptions` on the client.
- **All three server inits use it:** `sentry.server.config.ts` (Next,
Node), `sentry.edge.config.ts` (Next, edge), and `instrument.server.mjs`
(TanStack, Nitro). The TanStack init passes the commit SHA as `release`.
Next leaves it unset so the release from `withSentryConfig` still
applies.
- **The edge runtime now gets `beforeSend`** and the full `ignoreErrors`
list, which it didn't have before.
- `instrument.server.mjs` imports the builder by relative path. Studio's
tsconfig doesn't include `.mjs` files, so the `@/` alias may not resolve
there.

## Checklist

- [x] I have read
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)

Coverage Stats

2103 of 2478 branches covered (84.87%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

1 existing line in 1 file now uncovered.

2887 of 3247 relevant lines covered (88.91%)

200.85 hits per line