You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why are dependencies that are removed from the composer.json file still present in the installer path? Is this the intended behavior, or is there a solution to remove the dependencies from the installer path as well?
First, I will add a dependency to the installer path.
The text was updated successfully, but these errors were encountered:
vinkla
changed the title
Why is dependencies still present in the installer path after removal?
Why are dependencies still present in the installer path after removal?
Aug 18, 2023
Why are dependencies that are removed from the
composer.json
file still present in the installer path? Is this the intended behavior, or is there a solution to remove the dependencies from the installer path as well?First, I will add a dependency to the installer path.
{ "require": { "php": "^8.2" }, "extra": { "installer-paths": { "public/mu-plugins/{$name}/": [ "type:wordpress-muplugin", + "wpackagist-plugin/bugsnag" ] } }
Then, I will install the plugin by using the
composer require
command.The dependency has been installed correctly in the installer path. Next, I remove it from the
composer.json
file.Then I run
composer update
in the root of the project.The dependency has been removed from the
vendor
directory but remains in the installer path.Related issues: #82 #519
The text was updated successfully, but these errors were encountered: