Composer loading from cache

Question

i ran in a problem using composer for installing/uninstalling some dependencies in laravel which coming back after deleting them from composer.json and deleting the

Answer 1

composer caches packages under vendor/packagename convention. So you shouldn't run into any issue, just because the packagename is used in another vendor's package.

the cache locations are:

• Windows: %LOCALAPPDATA%\Composer\files\vendor\packagename
• Linux: ~/.composer/cache/files/vendor/packagename
• Mac OS: ~/.composer/cache/files/packagename

Answer 2

Don't edit your composer.json file manually to remove a package - it will remain in composer.lock.

Use composer remove to delete the old package then composer require to install the replacement.

Answer 3

In some cases (for example OpenSuse 42.1) all user cache are puts in:

~/.cache/

For the composer, the same as other applications, the cache path is:

~/.cache/composer/

So, just remove this folder as follow:

rm -fR ~/.cache/composer

Answer 4

So the only thing that worked for me on my Macbook was removing the package from my composer.json, deleting my composer.lock, running composer update, then adding the package back to composer.json, deleting my composer.lock(again), and running composer update (again). I had a local package in my instance of Laravel Nova that I changed to all lowercase from CamelCase and no matter what I did, it kept adding the package with the old CamelCase name. Didn't matter if I cleared caches or anything.

Answer 5

You can use the following command to clear the cache irrespective of the OS you are on:

php composer.phar clear-cache

or if composer is installed globally

composer clear-cache

Hope this helps

Answer 6

I think, you can run your composer commands with --no-cache option flag like

composer install --no-cache

Or

composer require <package-name> --no-cache

Or

composer update [<package-name>] --no-cache