[AyeshaWaseemAhmad]

The server init was only imported through injectScript('page-ssr', ...), which Astro adds to page modules but not to API endpoints. On a server that has not rendered a page yet, getClient() is undefined, so the request middleware skips the request and errors thrown by endpoints are dropped.

The middleware is now registered through a virtual module that imports the server init before re-exporting onRequest from @sentry/astro/middleware. With a server init file, the init is that file, which page-ssr imports as well. With the default generated snippet, the snippet lives in a virtual module that both the page-ssr injection and the middleware import. Either way the module is shared, so Sentry.init() still runs once, ahead of a page's own imports.

On a fresh Node-adapter build the first request to an endpoint now runs the init and the error is captured, on Astro 4, 5, 6 and 7 (also in astro dev on 7, on @astrojs/vercel serverless and on Cloudflare Pages). Before, nothing was captured until a page had rendered.

Cloudflare Workers is unchanged, because the Worker wrapper already initializes the SDK for every request. Netlify is unchanged too: its optional edge middleware is bundled into a separate Deno function and can't be detected here, and running the init there throws. Not covered: Netlify, autoInstrumentation.requestHandler: false, and errors thrown before the first request. An init file that throws at import time now fails endpoint requests as well.

Fixes #25729

[cursor]

Stale Bugbot comment from a previous run.

[logaretm]

This follows a similar approach to #25419, I think we can merge this then rebase the other one.

Did you verify this last bit you mentioned, which error is being thrown here?

Not covered: Netlify, autoInstrumentation.requestHandler: false, and errors thrown before the first request. An init file that throws at import time now fails endpoint requests as well.

[Lms24]

Thanks for opening this PR @AyeshaWaseemAhmad! This looked mostly good to me but i wasn't too happy about handling Netlify Edge and Vercel Edge differently. Since AFAIK, there's no way to detect if edge or node runtimes are used on both platforms, we can early return on server side init. I made that change on the branch.

We would need to look at edge runtime support differently long-term, similarly to how we support Vercel Edge in NextJS. But this is not on our priority list at the moment.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit d9801aa. Configure here.}