-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[remove] production deps which are only used in public code #75838
[remove] production deps which are only used in public code #75838
Conversation
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-operations (Team:Operations) |
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.
APM changes LGTM.
@spalger: do the package.jsons edited for APM impact the files that end up in the build, or was it just a consequence of running the script?
Pinging @elastic/apm-ui (Team:apm) |
@@ -1 +0,0 @@ | |||
../../../yarn.lock |
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.
Note: this was able to be removed since there are no longer any non-dev dependencies for it's package.json.
They impact the packages that are installed in |
@spalger alright, fwiw & as you probably know, the other packages in those files are only used for one-off scripts (that we run locally) and E2E tests. Should those not be moved to |
I think it makes sense to do that, would you mind submitting a follow up PR? |
…75838) Co-authored-by: spalger <spalger@users.noreply.github.com> # Conflicts: # package.json # x-pack/package.json
With #73591 we are now building Kibana Platform plugins from source when building them, which means we can move all the dependencies which are only used by code in
public
directories from dependencies to devDependencies. To determine which dependencies are eligible I wrote a script that I'm not planning to merge just yet but will likely get up in a PR shortly. This tool will allow us to enforce this going forward.For now, we should be able to drop a bunch of files from the build. When submitting the stats are pretty promising, the total file count of the distributable was reduced by 14,050 files, from 80,896 to 66,846.