Clever Geek Handbook

Composer returns after making changes

I am using composer to manage dependencies in a Drupal project. Some of the modules I have are in mercury storage. Once I am done composer install

, I can load my Drupal modules from their respective mercury repositories. The composer.lock file is also generated correctly.

Now let's say that I am committing to one of the repositories. After that, if I run it composer install

, I expect the changes to be checked in, so the repository will revert to the revision stored in composer.lock.

But that doesn't happen. The changes I made are saved. Am I missing something? Is it because I am using the mercury repository?

+3


source to share


1 answer


If I understood correctly, you changed something in yours vendor/project

, and you want to bring the changes back there, right? If so, I usually delete the directory vendor/project

and install the package again.



+3


source






More articles:


All Articles