Astro integration upload source map warning

[youngboy]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/astro

SDK Version

7.80.1

Framework Version

Astro 3.4.0

Link to Sentry event

No response

SDK Setup

    sentry({
      dsn: __DSN__,
      environment: process.env.VERCEL_ENV,
      release: `vivace@${version}`,
      debug: false,
      sourceMapsUploadOptions: {
        project: 'vivace',
        authToken: process.env.SENTRY_AUTH_TOKEN,
        telemetry: false
      }
    })

Steps to Reproduce

1. build
2. warning message occur
3. dashboard releases pages shows Source Maps[0 artifacts]

error

Expected Result

can find source maps file in release detail

Actual Result

error message:

[sentry-vite-plugin] Warning: No release name provided. Will not inject release. Please set the release.name option to identify your release.

[Lms24]

Hi @youngboy thanks for writing in! The "no release name" warning should be safe to ignore because source maps no longer need to be associated with a release. (although we should do something to omit the warning or carry over the release from the release option)

A couple of questions to debug this:

• Can you tell me, where in your project your built javascript is generated?
• Can you see *.map.(m)js files next to them?
• Which adapter (if any) are you using?
• Does this happen locally when you build your project (when running npm run build or similar)?

[youngboy]

@Lms24 Hi, thank you for your prompt reply.

I'm currently utilizing the Vercel adapter. During local builds, the process unexpectedly does not proceed to the sourcemap upload step.

However, the Vercel build logs indicate that despite some warnings, the sourcemap file is recognized and successfully uploaded. The issue arises in associating it with the release.

This can be verified on the dashboard page at "/settings/projects/vivace/source-maps/artifact-bundles/," as shown in this screenshot:

Additionally, in the release details page at "/releases/vivace%400.0.1/?project=4506240691798016," a similar situation is evident, as depicted in this screenshot:

[Lms24]

@youngboy You're using Sentry SaaS, correct? If yes, can you share a URL to an issue that should have source maps? This would help us debug this better. As I said, source maps don't have to be associated to the correct release anymore. We decoupled source maps and releases a while ago.

Also please let me know the answers to these two questions from my first reply:

• Can you tell me, where in your project your built javascript is generated? (e.g. <projectRoot>/dist)
• Can you see *.map.(m)js files next to the generated JS files?