[@sentry/vite-plugin] Benign log messages are being printed as errors (which fail the build)

[kaiyoma]

Environment

Vite: 5.4.10
@sentry/vite-plugin: 2.22.7

Steps to Reproduce

1. Build Vite and upload source maps to Sentry

Expected Result

Success

Actual Result

In the build output, there are some log messages that sound benign, but they're being printed as errors, which is causing our build to fail:

11:07:56  [log] vite v5.4.10 building for production...
11:07:56  [error] [sentry-vite-plugin] Info: Sending telemetry data on issues and performance to Sentry. To disable telemetry, set `options.telemetry` to `false`.
11:07:56  [log] transforming...

...

11:14:54      ~/dc706d4e-4b5e-44ff-8cf6-8f34254584a3-12.js.map (debug id dc706d4e-4b5e-44ff-8cf6-8f34254584a3)
11:14:54  [error] [sentry-vite-plugin] Info: Successfully uploaded source maps to Sentry
11:14:54  [log] ✓ built in 6m 58s

[kaiyoma]

This seems to be an issue in 2.22.7. If I downgrade to 2.22.6, the problem goes away.

[kaiyoma]

Might be this change causing the issue: #624

This seems like a very bad change because the wrong semantics are being used. Other tools (like task runners and monorepo tools) look for messages to stderr as part of their normal operation, and fail tasks/builds when those messages are detected.

[chargome]

Let's track this in getsentry/sentry-javascript#14879

[lforst]

This seems like a very bad change

I think it is very bad if tools rely on stderr to be empty. https://unix.stackexchange.com/a/331620

POSIX defines standard error as "for writing diagnostic output"

Stderr doesn't automatically mean error. It could be stuff like progress bars or debug messages.