Repository navigation
ERROR [sentry-rollup-plugin] Info: Successfully uploaded source maps to Sentry #14879
Description
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 SDK are you using?
@sentry/nuxt
SDK Version
^8.47.0
Framework Version
"nuxt": "^3.14.1592",
Link to Sentry event
No response
Reproduction Example/SDK Setup
I was using Sentry in a Nuxt project, and previously with Vue in Vite, I didn't encounter this issue.
The sentry-rollup-plugin reports an ERROR, but the output type is `Info.
And, in fact, there are no bugs when it is running.
like:
ERROR [sentry-rollup-plugin] Info: Using environment variables configured in ".env.sentry-build-plugin".
ERROR [sentry-rollup-plugin] Info: Sending telemetry data on issues and performance to Sentry. To disable telemetry, set options.telemetry to false.
ERROR [sentry-rollup-plugin] Info: Successfully uploaded source maps to Sentry
I checked the issues but didn't find similar cases, so it might be a problem on my end. I hope to get some help in resolving this.
sentry: {
sourceMapsUploadOptions: {
org: 'xxxx',
project: 'xxxxx',
authToken: process.env.SENTRY_AUTH_TOKEN,
sourcemaps: {
filesToDeleteAfterUpload: ['./dist/**/*.js.map'],
},
},
},
sourcemap: { client: 'hidden' },
Steps to Reproduce
I'm sorry, I don't know how to provide code to reproduce my situation.
If possible, what would you like me to provide? For my previous setups in Vite, I followed the simplest instructions according to the official website.
Expected Result
without ERROR
Actual Result
and
Metadata
Metadata
Assignees
Projects
- Status
Activity
s1gr1d commentedon Jan 2, 2025
Hello, thanks for reaching out!
All logs were directed to
stderrto not pollutestdout(someone reported an issue with knip).But I see that this is not ideal, as it's confusing to see an
ERRORmessage, when it's just an info. We'll discuss how to continue with that. My ideas for this:stdoutagain and add an option to silence those logs or to redirect them tostderr(for tools like knip)stdoutand add an option to redirect all logs tostderr(also for tools like knip)cc @lforst
lforst commentedon Jan 7, 2025
Imo just because something prints to stderr it doesn't necessarily mean it is an error. I don't think we should change this, at least in the bundler plugin layer. Is there a reason why these messages are prefixed with an
ERROR?s1gr1d commentedon Jan 8, 2025
Probably Vite, Rollup, zsh or bash prefix
stderrorconsole.errorwithERROR. But so far I couldn't find a source.When I
node -e "console.error('test message')", theERRORis not added, so I guess it's probably not coming from the terminal.kaiyoma commentedon Jan 10, 2025
I just reported something similar: getsentry/sentry-javascript-bundler-plugins#650
I think it's due to this change, which seems suspect: getsentry/sentry-javascript-bundler-plugins#624
s1gr1d commentedon Jan 13, 2025
I suspect Nuxt is changing the log output when something is logged as error: https://github.com/nuxt/nuxt/blob/main/packages/vite/src/utils/logger.ts#L27
We'll change this on our side to use
.info,.debugetc. in this PR: getsentry/sentry-javascript-bundler-plugins#652