Loader Script throws error when adding any Integration setting in code config, without it enabled in project settings

[jgs-thg]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

My org is looking to test Session Replays, to get better insight into our complex issues. We only want to log Errors, not general sessions, or dead/rage clicks, as we have a fairly large userbase, and the 10% default logging rate, will eat our budget/quota within 10-15 minutes.
So what we want to do, is adjust the setup of Session Replays, and push the setup to production, before enabling them in the project settings.
Unfortunately, adjusting the code config S, throws the error: You are using new Replay() even though this bundle does not include replay.. I think it should be possible to adjust the settings of an Integration in the Loader Script, without having the setting enabled, so that you can for a fact, deploy the settings to Production, before enabling the integration in the Projects settings.

Steps to reproduce:

1. Add an Integration setting to the Sentry.init(), such as replaysSessionSampleRate: 0 or the below code, while Session Replay is disabled in Project settings:

integrations: [
  new Sentry.Replay({
    maskAllText: true,
  }),
],

2. Note that Sentry now throws the below error from Replay.ts
   

Expected Result

Sentry throws no error, and allows adjustment of settings before enabling Session Replays as an Integration in the Project Settings.
This will also mean that the quote from the docs, is slightly more accurate:

The Loader Script allows you to configure some SDK features from the Sentry UI, without having to redeploy your application.
If we were able to change the settings directly from the Project Settings, this would make sense, but if we can't change the settings, before enabling the Integration, then we have to Deploy with the error active.

Actual Result

Sentry throws the error You are using new Replay() even though this bundle does not include replay. when enabling any setting related to it, without it enabled in the Project Settings:

Product Area

Replays

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-replays for triage ⏲️

[bruno-garcia]

Thanks for raising. @mydea had some ideas of what might be going on here. @mydea could you please elaborate?

[mydea]

Hello!

The message you are getting ("You are using new Replay() even though this bundle does not include replay.") is not an error, but just a console message telling you that replay is not actually enabled. This has been added to ensure users don't think that replay will capture anything if it is not actually included in the bundle. If you are deploying this consciously, you can safely ignore this message, it will not affect anything.

I'm closing this for now, if you have any other problems feel free to reopen!

[jgs-thg]

Hello!

The message you are getting ("You are using new Replay() even though this bundle does not include replay.") is not an error, but just a console message telling you that replay is not actually enabled. This has been added to ensure users don't think that replay will capture anything if it is not actually included in the bundle. If you are deploying this consciously, you can safely ignore this message, it will not affect anything.

I'm closing this for now, if you have any other problems feel free to reopen!

Perhaps it could then be changed from a console.error() to a console.warn() then? That way it would better communicate that it won't actually cause errors, and it'll still warn the user that it's not recording.