Misleading Source Map Errors During Build

[jd-carroll]

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/browser

SDK Version

8.0.0

Framework Version

No response

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

Also linking to these issues for completeness:

• SWC Core throws / prints (misleading) error swc-project/swc#8944 (where the error happens)
• opentelemetry/instrumentation-connect Has No Sourcemaps open-telemetry/opentelemetry-js-contrib#2199 (underlying cause)

When bundling code with @sentry/...@^8 you will see hundreds of errors that look like the following if your bundler is using @swc/core

  ERROR  failed to read input source map: failed to parse inline source map url
utils.js.map
Caused by:
    relative URL without a base
    at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/swc-0.273.27/src/lib.rs:385

Please use the links above to understand where the error happens versus what is actually causing the error.

It would be great to get some support from the Sentry team to have these issues resolved.

Expected Result

NA

Actual Result

NA