Closed JanPetr closed 11 months ago
Hi, we generally do not support use cases like these where you mess with the SDK in an unorthodox way. It would explode our maintenance efforts. I hope you can understand that.
We do however support the tree-shaking capabilities of all the commonly used bundlers, including webpack, which you seem to be using. I recommend you configure your bundler to tree shake, instead of doing crude string replacement.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
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
7.74.0
Framework Version
No response
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
We complile Sentry SDK like this:
Webpack config:
& load final file to broser and
Sentry.init
. When compiling including Sentry Replay, the browser doesn't record any sessions, but rather throws:When compling the Sentry SDK without Replay (running
sed -i -e "/export { Replay } from '@sentry\/replay';/d" sentry-browser/package/esm/index.js
with othersed
commands), everything works OK.Expected Result
No error thrown Session replays loaded in our Sentry.io
Actual Result
(version is older on screenshot, but works the same with 7.74.0)
And no session replays recorded.
Thank you for looking into it! 💙