Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Ashraam's avatar
Level 41

Composer takes ages to update

Hi everyone,

I'm trying to upgrade an app on laravel 6.x to 7.x (I've done this numerous time and it worked) but this project takes ages to update (I've let composer run for 20mn and still nothing)

Here is the packages I use

"require": {
        "php": "^7.2.5",
        "algolia/scout-extended": "^1.8",
        "caouecs/laravel-lang": "^4.0",
        "facade/ignition": "^2.0",
        "fideloper/proxy": "^4.0",
        "fruitcake/laravel-cors": "^2.0",
        "guzzlehttp/guzzle": "^6.5",
        "intervention/image": "^2.5",
        "jenssegers/date": "^3.5",
        "josiasmontag/laravel-recaptchav3": "^0.4.0",
        "laravel/framework": "^7.0",
        "laravel/scout": "^8.0",
        "laravel/slack-notification-channel": "^2.0",
        "laravel/socialite": "^4.3",
        "laravel/tinker": "^2.0",
        "lawnstarter/laravel-darksky": "^2.1",
        "league/flysystem-aws-s3-v3": "^1.0",
        "league/flysystem-cached-adapter": "^1.0",
        "predis/predis": "^1.1"
    },
    "require-dev": {
        "barryvdh/laravel-debugbar": "^3.2",
        "fzaninotto/faker": "^1.4",
        "mockery/mockery": "^1.0",
        "nunomaduro/collision": "^4.1",
        "phpunit/phpunit": "^8.5"
    },

I've use the regular command composer update -vvv and composer stuck at this output:

Something's changed, looking at all rules again (pass #54)

How could I fix this ?

Thank you

0 likes
25 replies
automica's avatar

@ashraam if you've manually adjusted composer.json, then its probably quicker to delete vendor directory and composer.lock and then run a composer install.

laracoft's avatar

My composer takes "forever" too, even with prestissimo. I have since learnt to live with it. LOL

Sinnbeck's avatar

Any chance you have xdebug enabled? I believe that will slow it down quite alot.

Sinnbeck's avatar

You can also try forcing it to use https (if it isnt doing so already)

composer config --global repo.packagist composer https://packagist.org
Sinnbeck's avatar

@laracoft Hehe yeah I can imagine :) Mine is super fast on all my servers. Only locally is it a bit slow (xdebug)

laracoft's avatar

@sinnbeck don't mind, what is your setup? I'm on W10 host with CentOS guest on VirtualBox and project files are W10 NTFS shared with the guest. I have been looking up and down for a speedier solution.

Sinnbeck's avatar

@laracoft My servers are running debian 9, on a virtual machine (Vmware) with just php and nginx installed directly on them

Locally I run ubuntu with docker containers

Using wls2 for virtualization?

laracoft's avatar

@sinnbeck I have been contemplating WSL2, but it doesn't play nice with VirtualBox.. it can only be one. Moving will affect my daily backups. It's too much to solve this slow composer problem.

Sinnbeck's avatar

@laracoft Totally understandable. Havent looked into it much, as I dont develop on windows. But I will need to get it tested soon, for laravel-served :)

Ashraam's avatar
Level 41

@automica Still the same message Something's changed, looking at the rules again pass(#26)

And when I look at the activity monitor, le php process takes 100% of the resouces oO

Ashraam's avatar
Level 41

@sinnbeck I've seen that thread before posting here yet it's not that helpful :/

I'm running the latest composer version (1.10.13)

laracoft's avatar

@ashraam What is the composer version?

  • Mine is Composer version 1.8.6 2019-06-11 15:03:05 and I can install L5.x to L7.x
  • On another server, Composer version 1.10.13 2020-09-09 11:46:34 to install L8.x
Ashraam's avatar
Level 41

@laracoft Here is the result of composer diagnose

Checking composer.json: OK
Checking platform settings: OK
Checking git settings: OK
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: OK
Checking github.com oauth access: OK
Checking disk free space: OK
Checking pubkeys:
Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0  87719BA6 8F3BB723 4E5D42D0 84A14642
Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B  0C708369 153E328C AD90147D AFE50952
OK
Checking composer version: OK
Composer version: 1.10.13
PHP version: 7.4.10
PHP binary path: /usr/local/Cellar/php/7.4.10/bin/php
OpenSSL version: OpenSSL 1.1.1g  21 Apr 2020
laracoft's avatar
laracoft
Best Answer
Level 27

@ashraam why not try this:

  1. Remove all the require and require-dev entries in composer.json
  2. Delete your entire vendor
  3. Manually do a composer require <package>, 1 by 1 starting with the most important one first, e.g. laravel/framework

If there is an issue on GitHub, I doubt you are going to find a good solution. The above steps are to help move you forward.

Ashraam's avatar
Level 41

So I digged into it (I clone the repo so I can do silly things) so it seems the problem was coming from the package jenssenger/date or caouecs/laravel-lang.

I keep you posted

Ashraam's avatar
Level 41

So I had to update jenssenger/date to the latest version, I've also removed the caouecs package and now it works fine !

Thanks for your help

raihan71's avatar

mine because PHP version in the codebase is not sync with the local so you need to check on your composer.json "require": { "php": "^7.3|^8.2",

Please or to participate in this conversation.