Sentry does not seem to recognize valid sourcemaps

[ktarmyshov]

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/sveltekit

SDK Version

"version": "9.15.0",

Framework Version

sveltekit "version": "2.20.8",

Link to Sentry event

https://konstantin-tarmyshov.sentry.io/issues/39901991/?project=4509255200669776&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&stream_index=1

Reproduction Example/SDK Setup

Dear Sentry Team,

I am using this adapter (https://github.com/kt-npm-modules/svelte-adapter-azure-swa) which I updated specifically to address this issue (sveltejs/kit#10040). The app itself is here https://github.com/kt-npm-modules/svelte-adapter-azure-swa/tree/main/tests/demo.

I confirmed that the source maps seem to work just fine by starting swa-cli in the debug terminal and was able to set and stop at the breakpoints, like for example, sentry example GET API, which throws the error. If I switch off the sourcemaps in the vite, so only sourcemaps are generated by the adapter from .svelte-kit/out "sources". I am not able to set the active breakpoints any more. So vscode recognizes the sourcemaps generated by the rollup.

This is what I get in Sentry

All green, but the Sentry does not show me any of the source code refs at all. This is the config:

		sentrySvelteKit({
			adapter: process.env.SWA ? 'other' : 'node',
			sourceMapsUploadOptions: {
				org: 'xxx',
				project: 'xxx',
				sourcemaps: {
					assets: ['./build/**/*', './func/**/*', './.svelte-kit/**/*']
				}
			}
		}),

what am I missing? Seems like a bug to me: VSCode recognizes sourcemaps, Sentry does not.

Konstantin

Steps to Reproduce

clone repo https://github.com/kt-npm-modules/svelte-adapter-azure-swa/tree/feat/sentry (branch feat/sentry)

npm run build:swa
npm run swa

Expected Result

I should be able to see normal mappings to the sources (stack trace)

Actual Result

I see trace in the final single azure function file.

[ktarmyshov]

So I was able to resolve most of the issues:

Before I was bundling into one file, now I let rollup to split into chunks. Somehow sentry does not pickup the sourcemaps for the bundled Azure Functions properly - one single file or chunks.

Sentry Example Frontend Error
Seems to show the line ref ok, will check at some point if more complicated project is handled ok
https://konstantin-tarmyshov.sentry.io/issues/40075355/?project=4509255200669776&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&stream_index=1

I however cannot connect the github sources.
This is the source file: https://github.com/kt-npm-modules/svelte-adapter-azure-swa/blob/main/tests/demo/src/routes/sentry-example-page/%2Bpage.svelte

I get the following error, when copy-pasting the url: Source code URL points to a different file than the stack trace

Sentry Example API Route Error
This one shows somewhat relevant info, but it seems it does not pick up the sourcemaps properly, it shows code of the bundled file.
https://konstantin-tarmyshov.sentry.io/issues/40075356/?project=4509255200669776&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&stream_index=0

[Lms24]

Hey, thanks for writing in! This might be related to sveltejs/kit#10040 indeed but not yet sure. Taking a look. Can't promise an ETA though as we're a bit busy with preparing for Svelte Summit and other tasks.

[ktarmyshov]

@Lms24
Hi, Lukas,

So using es as rollup output resolves the issue. Sentry picks up sourcemaps for both, frontend and backend.

https://konstantin-tarmyshov.sentry.io/issues/40278110/?project=4509255200669776&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&stream_index=0

https://konstantin-tarmyshov.sentry.io/issues/40278109/?project=4509255200669776&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&stream_index=1

So the issue can be closed.