You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello,
I tried to use sentry to track errors in a nextjs application, and I found that if the error occurred in the dynamic routes file of nextjs, the sourcemap could not be parsed, but it is parsed right in the static routes.
Then I tried a simple example:
The error in page/index.jsx can get the sourcemap, like this:
But the error in page/[domain].jsx can not get the sourcemap, like this:
I'm sure that the all the sourcemap files have been uploaded to the sentry.io artifacts.
The text was updated successfully, but these errors were encountered:
You might be hitting issues raised in #3896. We're discussing how to best approach this internally atm, will update soon!
Thanks your answer! I have seen the issues raised in #3896 . It mentions that "sentry config only uploads .next/static/chunks/pages instead of .next/static/chunks". But I upload all files in .next/static directory. Source maps only not work in nextjs dynamic routes, but work right in static routes. Is that the same problems?
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 label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
hello,
I tried to use sentry to track errors in a nextjs application, and I found that if the error occurred in the dynamic routes file of nextjs, the sourcemap could not be parsed, but it is parsed right in the static routes.
Then I tried a simple example:
The error in page/index.jsx can get the sourcemap, like this:
But the error in page/[domain].jsx can not get the sourcemap, like this:
I'm sure that the all the sourcemap files have been uploaded to the sentry.io artifacts.
The text was updated successfully, but these errors were encountered: