You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that we replace __SENTRY_SDK_SOURCE__ in the utils package already with npm, then we try to replace it again when building the CDN bundles, but at this point the magic string is already gone..
We should probably do this the same way as we do it for the debug flags, where we replace it twice.
The text was updated successfully, but these errors were encountered:
We used to replace `__SENTRY_SDK_SOURCE__` when we built
`@sentry/utils`, which means that we could not overwrite it anymore for
the CDN bundles, resulting in the SDK source being `npm` for the CDN
bundles.
This PR changes this so that this is correct now.
Closes#13435
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
8.26.0
Framework Version
No response
Link to Sentry event
No response
Reproduction Example/SDK Setup
No response
Steps to Reproduce
function getSDKSource() {
return "npm"
Expected Result
Should return
cdn
.Actual Result
Return
npm
The problem is that we replace
__SENTRY_SDK_SOURCE__
in the utils package already withnpm
, then we try to replace it again when building the CDN bundles, but at this point the magic string is already gone..We should probably do this the same way as we do it for the debug flags, where we replace it twice.
The text was updated successfully, but these errors were encountered: