-
Notifications
You must be signed in to change notification settings - Fork 1.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
Suggestion: reduce vendor libraries #1624
Comments
Hello! Thanks for submitting this ticket. It is true that the Google Library is massive. We'll check and see how this could become smaller.
|
The Readme of Google APIs Client Library for PHP has a section about Cleaning up unused services Cleaning up unused servicesThere are over 200 Google API services. The chances are good that you will not {
"require": {
"google/apiclient": "^2.15.0"
},
"scripts": {
"pre-autoload-dump": "Google\\Task\\Composer::cleanup"
},
"extra": {
"google/apiclient-services": [
"Drive",
"YouTube"
]
}
} This example will remove all services other than "Drive" and "YouTube" when IMPORTANT: If you add any services back in rm -r vendor/google/apiclient-services
composer update NOTE: This command performs an exact match on the service name, so to keep {
"extra": {
"google/apiclient-services": [
"Drive",
"YouTube",
"YouTubeAnalytics",
"YouTubeReporting"
]
}
} Should be fairly simple to add only what is needed... |
Hello! Thanks for researching and providing a suggestion for this optimization. This is really helpful :) Will review and update accordingly.
|
Would it be possible to reduce the size of the
vendor
folder?Right now, the folder has over 26,000 files.
There are more than 25,000 files in Google apiclient-services alone (
vendor\google\apiclient-services\src
)This includes APIs like Google Play and YouTube, which don’t seem necessary for EasyAppointments.
Could unused libraries be excluded or removed automatically during the build process?
This would make the project lighter and easier to deploy.
Thanks for considering this!
The text was updated successfully, but these errors were encountered: