dsn not optional with tunnel

[pquerner]

Hello,

reading the docs its worded like the dsn entry is optional, when using the tunnel option.
However I find that its not true.

Is there a way to hide the DSN in the frontend completely and let the tunnel enrich the DSN for the request?

For example this config

Sentry.onLoad(function () {
                Sentry.init({
// ...
                    dsn: '',
                    tunnel: '/tunnel/route',
// ...
                });
            });

is not working, it errors with Sentry Logger [error]: Transport disabled.

While the docs state

Sets the URL that will be used to transport captured events, instead of using the DSN.

(wording instead of)

from: https://docs.sentry.io/platforms/javascript/configuration/options/?original_referrer=https%3A%2F%2Fwww.google.com%2F#tunnel

When I give the correct DSN it works as expected and I get the call on my tunnel route.

Using @sentry/browser & @sentry/tracing & @sentry/replay 7.75.1 (538890b) ES6 /w debug (minified) from https://browser.sentry-cdn.com/7.75.1/bundle.tracing.replay.debug.min.js

[AbhiPrasad]

We still need a DSN setup even when using a tunnel due to some sdk limitations. This is something we should work on improving in our next major version of the SDK.

For now I opened a docs PR to make the docs more clear getsentry/sentry-docs#8337.

[pquerner]

Thanks for confirming and updating the docs. :)

Are there plans to change that behaviour? Or can it be changed even.

[AbhiPrasad]

For the time being no plans, but it's something we'll think about as part of our 8.0.0 release