[nextjs] support `assetPrefix` option

[klapec]

Package + Version

• @sentry/cli: 1.71.0
• @sentry/nextjs: 6.15.0

Description

I have my Next.js (12.0.4) app served with an assetPrefix option in the next.config.js set to point to a custom CDN location.

Unfortunately, my on-premise Sentry instance seems to be not matching the sourcemaps that are being uploaded every time I do a production app build with the exception trace filename.

Here's the filename that I see in the issue's exception trace filename: /multi-prod/B991483/react/_next/static/chunks/pages/_app-40564a69361d2d0a.js

Here's the filename that I seen in the project's Source Maps > Archive page: ~/_next/static/chunks/pages/_app-40564a69361d2d0a.js (and a corresponding .js.map file: ~/_next/static/chunks/pages/_app-40564a69361d2d0a.js.map)

The actual script is served from https://cdnprod.example.com/multi-prod/B991483/react/_next/static/chunks/pages/_app-40564a69361d2d0a.js

And the script has a following sourceMappingURL comment: //# sourceMappingURL=_app-40564a69361d2d0a.js.map.

Is this all correct? The issue here is that every issue has problems with "Source code was not found".

[mrdimidium]

I am experiencing such difficulties - the application is used assetPrefix, which is not taken into account when downloading the release.

I noticed that the toolkit is already checking the basePath. Do you think it is possible to take into account assetPrefix in a similar way?

[github-actions]

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 🥀

[klapec]

This is still relevant as Sentry is unaware of my source maps - which makes debugging quite difficult.

[mrdimidium]

This is still relevant for me, I can't use this package, I have to maintain my own configuration. Is there any way I can help in researching the problem?

[colbyjohnson-care]

I have to maintain my own configuration. Is there any way I can help in researching the problem?

This is relevant for us as well. @nikolay-govorov any tips you have to begin on a placeholder configuration to get this working?

[smeubank]

Hi all

we are taking this into our backlog to review, we are aware of the issue and appreciate the need to keep the ticket open.