Problem with Nuxt source maps generation #15160
Comments
|
I'm experiencing a similar issue after two days of investigating the Sentry documentation and code, with a slight difference: While you received a (I'm genuinely exhausted from adding source maps to Sentry and have basically given up at this point) Versions used:
Attached are my configuration files:
When generating the project, I encountered this error: here is warning "Missing source map with a matching Debug ID" in site Hope this helps in troubleshooting the issue. |
|
Hi @adiantek @MirzaeiDev, thanks for filing this. I just had a look at it seems like setting the We'll have to dig deeper into why this is the case tho. @MirzaeiDev you shouldn't have to add the |
|
Hi, My sentry.client.config.ts file My package.json My nuxt.config.ts file sourcemap uploaded to Sentry But when a problem occurs, sourcemap are not matched.
Please, what is the problem, how to make the sourcemap work? |
|
@Azirafel17 Thanks for sharing the screenshots. Can you share the link to the Sentry event? If you don't want to post it here, you can send it to me via mail (without whitespaces): sigrid . huemer [at] sentry . io |
|
Hello, Sigrid. |
|
Hello @Azirafel17, And about your "Unhandled Rejection" event in the screenshot: This is a synthetic event without an attached stack trace. Seems like you have a Promise that is not rejected with an error. If the Promise would throw an error when it is rejected, you would see a stack trace. But this is not related to source maps, since source maps are only needed when there is a stack trace. |
|
Hello @s1gr1d |
|
Hi @s1gr1d My event in Sentry My event json file My upload sourcemap The error call options that I used: I can't achieve the result of displaying the error as shown in the screenshot below: |
About your code: It looks alright how you call it. And you are running the build output of your app? Can you maybe share a small reproduction example? Because I am not able to reproduce this unless I am in dev mode (which does not upload source maps). |
|
@s1gr1d, In the information_for_problem_analysis folder, under the parsing information (logs, screenshots, events, sourcemaps) |
|
@s1gr1d 🎉🎉🎉 You are beautiful! The problem was the type of application launch. Nuxt component Pinia Thank you so much, after 2 weeks I found peace. Can this information be added to the documentation, because this nuance is not obvious? |
getsantry
bot
added
Waiting for: Product Owner
and removed
Waiting for: Community
labels
getsantry
bot
moved this from Waiting for: Community
to Waiting for: Product Owner
in GitHub Issues with 👀 3
Yes, that would be useful. However, it's already in the documentation here. |
|
Thanks again @s1gr1d 😊 Have a nice day) |
|
@adiantek @MirzaeiDev You originally commented on this issue. Do you still experience problems with source maps or were you able to resolve those issues? |
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
…ap settings (#15859) There is a total of 6 settings in Nuxt where you can disable/enable your source maps. This is not only difficult to understand when writing and maintaining the logic for this. It may also be hard to debug stuff for users.  There is this discussion around Nuxt source maps: #15028 And this issue: #15160 A problem with the current setup was not only the difficulty to understand all of this but also it sometimes just overwrote stuff you didn't want it to. Like in the default case of Nuxt, `sourcemap.server` is `true`, but as `nitro.rollupConfig.output.sourcemap` is always undefined, Sentry would overwrite this setting to `'hidden'`, even though the source maps were enabled already. --- The only two relevant options in Nuxt are the [root-level sourcemap options](https://nuxt.com/docs/guide/going-further/debugging#sourcemaps). Those settings will propagate to nitro, vite and rollup. As we overwrite the source maps setting if the setting is undefined, only the basic Nuxt source map settings (linked above) are taken into account for that from now on.
…ap settings (#15859) There is a total of 6 settings in Nuxt where you can disable/enable your source maps. This is not only difficult to understand when writing and maintaining the logic for this. It may also be hard to debug stuff for users.  There is this discussion around Nuxt source maps: #15028 And this issue: #15160 A problem with the current setup was not only the difficulty to understand all of this but also it sometimes just overwrote stuff you didn't want it to. Like in the default case of Nuxt, `sourcemap.server` is `true`, but as `nitro.rollupConfig.output.sourcemap` is always undefined, Sentry would overwrite this setting to `'hidden'`, even though the source maps were enabled already. --- The only two relevant options in Nuxt are the [root-level sourcemap options](https://nuxt.com/docs/guide/going-further/debugging#sourcemaps). Those settings will propagate to nitro, vite and rollup. As we overwrite the source maps setting if the setting is undefined, only the basic Nuxt source map settings (linked above) are taken into account for that from now on.
mydea
changed the title
|
Why was this issue closed? This issue hasn't been touched recently and no longer seems relevant. Please feel free to leave a comment if you think this issue should be reopened. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nuxt
SDK Version
8.51.0
Framework Version
Nuxt 3.15.2
Link to Sentry event
No response
Reproduction Example/SDK Setup
Steps to Reproduce
npx nuxi@latest init projectnamecd projectnamenpx nuxi@latest init projectnamenuxt.config.tsto upload only generated.map(code from SDK Setup)npm run generateExpected Result
Source maps from generated page should be uploaded. Sentry/nuxt uploads only from nuxt-server.
sentry-rollup-plugintrying to upload source maps beforePrerendering 3 initial routes with crawler.Actual Result
The text was updated successfully, but these errors were encountered: