-
-
Notifications
You must be signed in to change notification settings - Fork 413
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
Renaming vendor breaks composer install #519
Comments
One thing that actually helps is using vendor names in custom path, e.g.
but that violates wordpress plugin directory structure as plugins should be flat. |
What I've been doing in WordPress projects is prepending the vendor name to the package/install name:
I avoid this for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
"web/app/plugins/{$name}/": ["type:wordpress-plugin"]
a/my-package
tob/my-package
composer remove a/my-package && composer require b/my-package
composer install
What happens:
Composer uninstalls
a/my-package
, then installsb/my-package
, but as a last step, it removesmy-package
directory (therefore removes the newly installed one)`.Expected behaviour:
Old package will be removed, and new plugin will be installed.
The text was updated successfully, but these errors were encountered: