m/h: What is our rationale behind moving away from npx astro add @sentry/astro? Despite us instructing people to declare separate client|server config files, the astro CLI would still automatically register the intgration in astro.config.mjs for users.

Users are probably familiar with adding Astro integrations and we're also listed in their official integrations directory: https://astro.build/integrations/?search=sentry

good point, I'll update that

the only thing that bugged me here is that we have another code snippet for adding profiling

l/no action required: I find it a bit unfortunate that the advanced config section is also on the Getting Started page. We might want to consider moving this somewhere else. Previously, "Manual Setup" gave us the option to write all of this down but still have a short and concise "Getting Started" page. I think this might be worth to revisit later, potentially after the rework on the "Getting Started" pages (contrator?) of other SDKs is in a good state 🤔

yeah was not sure where to put this tbh, I guess just adding an advanced config sub page also would not make sense?

@Lms24 merging this so we get this out for now, we can do a follow up!

sorry, for not reviewing this in time! I'm fine with leaving it as-is for the moment