-
Notifications
You must be signed in to change notification settings - Fork 160
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
Composer runs twice on first install of plugin #170
Comments
Running into this as well. |
This is a classic "chicken and egg" problem. The second run is needed because composer-merge-plugin is not available to Composer until it has been installed. If the second installation run was not invoked by the plugin itself then no packages installed by composer-merge-plugin would be installed until a second manual run was made. On the first pass, composer-merge-plugin as well as any dependencies specified directly in the project's |
Related: #145 |
#252 is a potential work around for this issue. The proposed feature would introduce a new merge-plugin option to skip the second run and only use the composer.lock provided dependencies. This would not remove the chicken and egg problem outlined in #170 (comment), but it could be added to composer.json after first installing composer-merge-plugin and allowing it to process an update to add any dependencies from included files. |
When installing for the first time (from a lock file), the plugin triggers an additional install:
This doesn't seem necessary, at least not when you're installing from a lock. We'd like to avoid it because it also triggers the post install scripts twice...
The text was updated successfully, but these errors were encountered: