Shulou(Shulou.com)06/02 Report--

This article mainly introduces the solution of slow composer installation dependence, which is very detailed and has a certain reference value. Friends who are interested must finish it!

Composer installation depends on slowness. Check the detailed execution log of composer.

Install composer dependencies on windows WSL

Composer install

Found that the execution is extremely slow, suspected not to go to the domestic image, but directly visit the github.

Need to be able to see the execution log of composer

Composer-h

Discovery of parameter support for composer

-v | vv | vvv,-- verbose Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

So

Composer-vvv install

Sure enough, they all walked, github.

Installing backpack/crud (3.2.27): Downloading https://api.github.com/repos/Laravel-Backpack/CRUD/zipball/54fb667a1cf64f4c53f8a90a3752d1f964fdec6fDownloading (connecting...) Following redirect (2) https://codeload.github.com/Laravel-Backpack/CRUD/legacy.zip/54fb667a1cf64f4c53f8a90a3752d1f964fdec6f

After I updated it to https://laravel-china.org/composer 's domestic mirror source, I found that the installation was still github.

Check it out, it turned out to be the problem with composer.lock, delete composer.lock, and then run composer install to regenerate. The reason is that composer.lock caches the previous configuration information, which causes the new mirror configuration to be invalid.

These are all the contents of the article "composer installation depends on slow solutions". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.