Difference between #10 and #18 of
What to do when composer fails to update your vendor packages?

Revision #18 has been created by Kartik V on May 5, 2014, 7:55:27 PM with the memo:

Formatting
« previous (#10) next (#19) »

Changes

Title unchanged

What to do when composer fails to update your vendor packages?

Category changed

How-toTutorials

Yii version unchanged

Tags unchanged

Yii2, yii2, composer, corrupt, update, package, reinstall

Content changed

Problem Statement ----------------- DoHave you faced some of these problems when using composer with your Yii 2 installation?

- Running a `composer update` does not fetch any new packages (even though the source is updated)
[...]
Normally you need to check the package sources and if your network connectivity is stable when doing a composer update. But in most such cases above (even though rare), you may need to refresh and reinstall your composer packages.

The normal approach is to reinstall packages. DIn order to reinstall packages using composer, you can do the following: 1.**Step 1:** Backup your `vendor` folder under your app root, and delete all files in the `vendor` folder, except `.gitignore` if it exists.
 
2.  
 
**Step 2:** Backup your `composer.lock` file on your app root, and delete it.
 
3.  
 
**Step 3:** Run the following command from your application root:.

~~~
php composer.phar install --prefer-dist
~~~
[...]
0 4
36 followers
Viewed: 50 833 times
Version: 2.0
Category: Tutorials
Tags: composer, corrupt, package, reinstall, update, Yii, yii2
Written by: Kartik V
Last updated by: Kartik V
Created on: May 5, 2014
Last updated: 10 years ago
Update Article
Revert to #10 | Revert to #18

Revisions

View all history