Skip to content
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

[BUG] - InitSetup folder adds 44.5MB of extra 'stuff' to the libs #441

Open
dingo-d opened this issue Nov 6, 2024 · 2 comments
Open

[BUG] - InitSetup folder adds 44.5MB of extra 'stuff' to the libs #441

dingo-d opened this issue Nov 6, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@dingo-d
Copy link
Collaborator

dingo-d commented Nov 6, 2024

Not sure if you're aware but the folder InitSetup you've added to it increased the libs size by a huge amount.

From what I see, these are only CLI commands, so it would be cool if, when running composer install --no-dev (production build), this folder would be excluded from bundling, as it's not important for the production build of any theme/plugin.

I only noticed this because I went to update a plugin, and noticed that my zip size went from 12MB to 28MB, which was super suspicious.

@dingo-d dingo-d added the bug Something isn't working label Nov 6, 2024
@mbmjertan
Copy link
Collaborator

This seems to be the theme initializer (boilerplate), so makes sense to exclude from --no-dev installs

@dingo-d
Copy link
Collaborator Author

dingo-d commented Nov 7, 2024

I don't think there are script events that target --no-dev install, but there is post-autoload-dump, which could be used to trigger some script that will clean any file that is not needed for production?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants