Enable stack trace for server side api request on Payload CMS working with Next.js with Standalone mode with new relic

[jjimenez22991]

Hi! I've Payload CMS instance workinng with Next.js v15.2.3 deployed on a dockerized environment with the "output" mode configured as standalone for performance reasons, with an api created and I wonder if it's possible to have a better stack trace. In server side when an error is reported is appearing like this and it's difficult to debug:

UnauthorizedError: Unauthorized
at tX (/service/.next/server/chunks/8651.js:1:70129)
at async /service/.next/server/chunks/3137.js:1:60864
at async p.context.headers (/service/.next/server/chunks/3137.js:1:61101)
at async /service/.next/server/chunks/3137.js:1:58459
at async to.do (/service/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:18605)
at async to.handle (/service/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:23632)
at async doRender (/service/node_modules/next/dist/server/base-server.js:1513:42)
at async NextNodeServer.renderToResponseWithComponentsImpl (/service/node_modules/next/dist/server/base-server.js:1915:28)
at async NextNodeServer.renderPageComponent (/service/node_modules/next/dist/server/base-server.js:2393:24)
at async NextNodeServer.renderToResponseImpl (/service/node_modules/next/dist/server/base-server.js:2430:32)
I've read and configured everything mentioned here:

• https://nextjs.org/docs/pages/api-reference/config/next-config-js/output#experimental-turbotrace
• https://www.highlight.io/blog/lw5-next-js-server-sourcemaps
• sourcemaps not being generated vercel/next.js#28897

I tried sending the source maps to new relic but we continue with the issue. Also I saw not all the files generates .map file when those ones are enabled.

Thanks in advance.