-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Add @kbn/analytics-client
to the shared libs to test any bundle size improvements
#130027
Comments
Pinging @elastic/kibana-core (Team:Core) |
+1 to adding it as a shared dependency. This can be done at any point so no harm holding until it is actually used in multiple places |
AFAIK, it'll only be imported in @elastic/kibana-operations do you think it's enough of a reason to move it to the shared library? |
FWIW, The shippers are registered during the |
If it's already loaded by core on every page load then there's little reason to keep it out of the shared-ui-deps. |
Thanks for confirming! I'll create a quick follow-up PR next week to address this issue. |
@elastic/analytics
to the shared libs to test any bundle size improvements@kbn/analytics-client
to the shared libs to test any bundle size improvements
Is this still needed? When we initially created it, it referred to As we split the package into 3: The shippers depend on some types of If you think it's still worth giving it a shot, I can try to put a quick PR to test if there's any benefit. What do you think? |
It seems fine then, we can probably close this |
I'll close then. Please, feel free to reopen if you think it's still worth trying. |
Given we know that the
@elastic/analytics
will at least always be imported bycore
, should we move it to the shared libs?Originally posted by @pgayvallet in #129927 (comment)
The text was updated successfully, but these errors were encountered: