Contradicting warnings between @sentry/astro and sentry-vite-plugin

[pawelgrzybek]

Environment

"@sentry/astro": "^10.36.0",

Steps to Reproduce

I setup a basic astro build using Astro and using @sentry/astro as per Sentry documentation. When I set it up like this...

    sentry({
      project: "website",
    }),

I received this warning.

18:40:42 [WARN] [@sentry/astro] You passed in additional options (project) to the Sentry integration. This is deprecated and will stop working in a future version. Instead, configure the Sentry SDK in your `sentry.client.config.(js|ts)` or `sentry.server.config.(js|ts)` files.

so i removed the project field, rerun and then I got this on the source maps upload phase.

[sentry-vite-plugin] Warning: No project provided. Will not create release. Please set the `project` option to your Sentry project slug.
computing gzip size (5)...[sentry-vite-plugin] Warning: No project provided. Will not upload source maps. Please set the `project` option to your Sentry project slug.

Expected Result

Warnings if any should be consistent and plugins that belong to the same family of framework should agree on the expected result. This is confusing for the end user.

Actual Result

Confusion as per my description.

[linear]

BUNDLER-99

JS-1536

[JPeer264]

Thanks @pawelgrzybek for raising this issue. I just opened #18947 that fixes that behavior

[pawelgrzybek]

Awesome, thanks.

So you pulled a few other keys out of doNotUseTheseOptions. So it is fine to use org, project, authToken etc as part of the sentry integration initialisation? I think what will improve user experience and avoid some future confusion. Thanks a lot @JPeer264

I think using a more descriptive name like deprecatedOptions better represents the intention. The next person won't need to read the deprecation notice to understand why they shouldn't be used. But this is nitpicky. Thanks for that!

[JPeer264]

@pawelgrzybek that is an amazing feedback thank you. I just changed it to deprecatedOptions thx

So it is fine to use org, project, authToken etc as part of the sentry integration initialisation?

Yes exactly. I'll clarify the docs next week about this.