Good content takes time and effort to come up with.

Please consider supporting us by just disabling your AD BLOCKER and reloading this page again.

Composer Install v/s Composer Update

08th May 2020 3 mins read
Share On     Share On WhatsApp     Share On LinkedIn

In this article you will learn what is the difference between composer install & composer update.

  1. Composer Update v/s Composer Install
  2. When To Use Which Command
  3. Tip while using composer


You need to have composer installed in your computer or server.

Even if you don't have any knowledge on the composer thats totally fine. I have written an details article for it here What Is Composer? How Does It Work? Useful Composer Commands And Usage.

Composer Install v/s Composer Update

Composer Update ( Use only during development & testing mode )

When you do composer update it will check for composer.json file and updates all the packages/libraries that are listed in it & once the packages are updated it will rewrite new updates in composer.json & composer.lock file by deleting old package updates.

Basically the following process

  1. Read composer.json
  2. Remove installed packages that are not required in composer.json
  3. Check latest versions of required packages in composer.json from
  4. Install the latest versions of your packages
  5. Update composer.lock with installed packages version & even update composer.json file with it
  6. composer install

Eg: Lets take an example of this, in your composer.json file you may have this

"require": {
    "guzzlehttp/guzzle": "^6.3",

Think that you have installed guzzle package for CURL requests 2 months back in your project with version was 6.3.0.

When you do composer update composer will go and check in its repositories if any new update available for the guzzle package. If any new update like 6.3.2 then it will go ahead and update the package to 6.3.2.

Along with updating the package it will also update the composer.json and composer.lock file.

Composer Install (Can use during development, testing & production environment)

When you do composer install it will check for composer.lock file and install all the packages/libraries that are listed in composer.lock file.

This command won't update anything like composer update.

  1. composer.lock file 
  2. If it does not exists then run composer-update and create it
  3. If exists then read composer.lock file for installation fo packages
  4. Install the packages specified in the composer.lock file

When To Use Which Command

Composer Install (Production, Development & Testing)

Use this command in any of the product stages ie Production, Development & Testing. As this wont have any affect on the composer.json & composer.lock file.

Composer Update (Development & Testing)

Use this command in Development & Testing stages of your product only. As this will update the composer.json & composer.lock files.

Be very cautious with this command

Tip While Using Composer

Few of the tips I would like to give you guys from my experiences are as follows

1) Add vendor folder in .gitignore

Yes! You saw it right. Make sure to put vendor in .gitignore file if using GIT else similar file with other version control. When you use version control make sure to only commit composer.json & composer.lock file.

If any of your colleagues needs to use this vendor folder then let them run composer install or composer update as per needs

2) Commit composer.lock file to production

Don't neglect composer.lock while committing your code to production. Because in production you will be doing composer install, if it doesn't find composer.lock then it will update the composer.json file.


Hope this was helpful for you.

Author Image

Channaveer Hakari

I am a full-stack developer working at WifiDabba India Pvt Ltd. I started this blog so that I can share my knowledge and enhance my skills with constant learning.

Never stop learning. If you stop learning, you stop growing