-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NextJS package does not upload source-maps on WINDOWS #4829
Comments
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. |
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 |
Hi @AbhiPrasad, thanks for taking the time to review my post :) I want to note that I did already try configuring it with the Here is what I have in my
and this is how my
To my eyes, it looks like it matches the requirements of the CLI configuration steps outlined in the docs: Is there something I am missing? |
@AbhiPrasad I've tested the exact same workflow now on an Ubuntu VM, and confirmed that it does try to upload there. I shared my branch with a coworker who runs on Mac and also verified it tries to run there, so it looks like specifically it doesn't work on windows. Looks like there is a potentially relevant bug here: #4720 But I have WSL installed, so I don't think that is the issue here. Any thoughts? I feel this is now an actual bug and not just a documentation issue, unless Windows support for the |
#4720 is related to SDK development - I don't think it applies here. I think you're right it could be more than a docs issue - I'll expand the scope. The issue might be with https:/getsentry/sentry-webpack-plugin (which is what the NextJS SDK uses under the hood) or https:/getsentry/sentry-cli/ (which does the actual uploading of source maps). @kamilogorek the webpack plugin/sentry-cli should work fine in Windows or WSL right? |
Yes, it should work just fine in most environments, including windows. Can you set |
I experienced the same problem and could narrow it down to v 6.17.0
With ~6.17.0 and above there is no output at all with SENTRY_LOG_LEVEL=debug A temporary solution is to downgrade to ~6.16.0 |
Same problem here with @sentry/nextjs 7.11.1. It does not upload on Windows but it does on Ubuntu. It checks if the file exists "node_modules/@sentry/cli/sentry-cli" exists: https:/getsentry/sentry-javascript/blob/master/packages/nextjs/src/config/webpack.ts#L447 But it does not, at this location. However sentry-cli is at node_modules/@sentry/cli/bin/sentry-cli and node_modules/.bin/sentry-cli Just replacing "@sentry/cli/sentry-cli" with "@sentry/cli/bin/sentry-cli" in webpack.ts makes it work on Windows. |
Any updates on this? Core feature doesn't work on biggest desktop OS |
@h0gar - |
Is there an existing issue for this?
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
next build
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 usingcross-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 thesentry-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.The text was updated successfully, but these errors were encountered: