-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(core): Deprecate hub.bindClient()
& makeMain()
#10188
Conversation
Instead, users should use `setCurrentClient()` & `client.init()`.
size-limit report 📦
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a fan of setCurrentClient
but it's where we're at.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a fan of setCurrentClient
but it's where we're at.
@@ -94,7 +94,7 @@ module.exports = [ | |||
path: 'packages/browser/build/bundles/bundle.tracing.min.js', | |||
gzip: false, | |||
brotli: false, | |||
limit: '100 KB', | |||
limit: '105 KB', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
side note (no action required): I really hope that our bundle size will decrease to ~v7.0.0 levels once we removed all the deprecated stuff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, it will decrease for sure - right now we need to add a certain degree of duplication, sadly, which will go away again! I'm very optimistic in this regard.
Instead, users should use
setCurrentClient()
&client.init()
.For now, we can't fully replace our own test usages of this everywhere, as we need it to test a clean hub state. But for users, there should be a reasonable path forward for 99% of cases. I added a docs page outlining how the different scenarios will work in v8 (and already should work now, too).