NextJS package does not upload source-maps on WINDOWS

[yoont4]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/nextjs

SDK Version

6.19.3

Framework Version

6.19.3

Link to Sentry event

No response

Steps to Reproduce

1. Setup project following NextJS docs: https://docs.sentry.io/platforms/javascript/guides/nextjs/
2. Run next build
3. Run next start

Expected Result

Source-maps uploaded

Actual Result

No source-maps uploaded.

I'm not sure what I'm supposed to see either to confirm they get uploaded or not.

I've manually configured a release version in the sentry.client/server.config.js files to see if that was the issue, and that didn't change anything. All it did was make an empty release bucket with no artifacts.

I've tried setting the SENTRY_RELEASE environment variable using cross-env and a .env file (in separate attempts) and they both did nothing.

I've tried manually setting the release field in the sentryWebpackPluginOptions as well to see if the sentry-webpack-plugin needed it, and that did nothing.

I've watched the netlify and vercel videos on sentry's youtube channel, and they both just refer to some netlify or vercel plugin to handle it. But the docs clearly state that @sentry/nextjs will automatically handle the sourcemap uploads! I am completely at a loss. I see 0 output, no errors, no warnings, nothing.

[SheaBelsky]

I posted a similar question to this a few days ago: #4812

There's a lack of clarity on how Sentry sourcemaps are supposed to be handled for a CI/CD environment on Next.js apps. Not every Next.js app runs on Vercel, and documentation/clarity for how other CI/CD platforms are intended to work would be great.

[AbhiPrasad]

Hey, thanks for writing in. Great feedback - we recognize that our documentation can be improved for non-vercel environments for NextJS, appreciate the further context though. I'll be backlogging this as a documentation task for us to work on.

You'll have to use config files or environmental variables (like Sentry auth token, org name, project name) to configure Sentry CLI to upload the assets: https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#configure-sentry-cli

You can get more details on the Sentry Auth Token and how it's generated here: https://docs.sentry.io/product/cli/configuration/#to-authenticate-manually

[yoont4]

Hi @AbhiPrasad, thanks for taking the time to review my post :)

I want to note that I did already try configuring it with the sentry.properties and .sentryclirc file mentioned in your link. I've generated an auth token with the default permissions + project_write just in case, and that is what I set in the .sentryclirc file.

Here is what I have in my sentry.properties file:

defaults.url=https://sentry.io/
defaults.org=<redacted>
defaults.project=<redacted>
cli.executable=../node_modules/@sentry/cli/bin/sentry-cli

and this is how my .sentryclirc file looks:

[auth]
token=<redacted>

To my eyes, it looks like it matches the requirements of the CLI configuration steps outlined in the docs:
SENTRY_URL, SENTRY_ORG, SENTRY_PROJECT, SENTRY_AUTH_TOKEN

Is there something I am missing?