Sentry-javascript: [raven-node] Sourcemaps were uploaded but Sentry displays only generated JavaScript code

Created on 12 Jun 2018 · 6Comments · Source: getsentry/sentry-javascript

ref: https://github.com/getsentry/raven-node/issues/435

Source

HazAT

👍4

Most helpful comment

@kamilogorek you asked DMV007 to create a repo for you in the referenced issue which he did (https://github.com/DMW007/sentry-typescript-sourcemaps-bug-poc) and to which no reponse came from the sentry side.

mrnagydavid on 11 Sep 2018

👍3

All 6 comments

Too hard to tell anything without a repro case. Closing it for now, as we don't know if it's still relevant with new SDK. Feel free to reopen if it is.

kamilogorek on 4 Sep 2018

mrnagydavid on 11 Sep 2018

👍3

@mrnagydavid as it's not JS SDK issue, but rather sentry's docker instance itself. It's just not a correct place to report this kind of issue. (my bad about "no repro case" part). Since the last post in the original thread, Sentry 9 was released and is available on the Docker's hub, which may fix the initial issue.

kamilogorek on 11 Sep 2018

There doesn't seem to be great support. I am experiencing the same issues with Sentry 9.

jjcallis on 9 Jan 2020

I also have problem with NodeJS Source Maps. I have two project, one is standard JavaScript code for frontend and second one is NodeJS server code. Both project are builded by Webpack with almost the same config. The only difference is that in frontend code I use @sentry/browser plugin while in NodeJS @sentry/node.
Errors from frontend code displays with code from source maps without any problems while backend code is shown only in its minified form.
I was using this guide: https://blog.sentry.io/2019/02/20/debug-node-source-maps also without any result.