Upload Javascript SourceMaps to Datadog #42659
Unanswered
brunosalgueiro
asked this question in
Help
Replies: 2 comments 4 replies
-
I think the problem could be in |
Beta Was this translation helpful? Give feedback.
2 replies
-
What bothers me is that I have to do two builds or delete the source maps from the nextjs build if I don't want to leak my server side code. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, everyone!
We are using Datadog to monitor user browser sessions and detect any errors.
Everything is tracked as expected, but because files are minified, we'd like to analyze errors using sourcemaps.
We discovered datadog documentation on how to upload sourcemaps.
https://docs.datadoghq.com/real user monitoring/guide/upload-javascript-source-maps/?tab=webpackjs
We tried to override build configurations on Vercel to get sourcemaps.
next build && npx -y @datadog/datadog-ci sourcemaps upload /vercel/output/_next/static --service={our-service} --release-version={deploy-version} --disable-git --minified-path-prefix=https://fluencypass.com/_next/static
We believe that the output directory is being generated after the build, which is why datadog-ci sourcemaps cannot find any sourcemaps files.
Has anyone attempted something similar with datadog + nextjs?
Beta Was this translation helpful? Give feedback.
All reactions