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

neon_beam's avatar

Errors while 'composer update'

I want to run this project locally github project When I composer update I get those errors:

Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install fruitcake/laravel-cors v2.0.1 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.0.2 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.0.4 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.0.5 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.1.0 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.2.0 (conflict analysis result)
    - illuminate/support[v5.6.0, ..., v5.8.36] require php ^7.1.3 -> your php version (8.2.7) does not satisfy that requirement.
    - illuminate/support[v6.0.0, ..., v6.19.1] require php ^7.2 -> your php version (8.2.7) does not satisfy that requirement.
    - illuminate/support[v7.0.0, ..., v7.28.4] require php ^7.2.5 -> your php version (8.2.7) does not satisfy that requirement.
    - illuminate/support[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.2.7) does not satisfy that requirement.
    - Root composer.json requires fruitcake/laravel-cors ^2.0 -> satisfiable by fruitcake/laravel-cors[v2.0.0, ..., v2.2.0].
    - Conclusion: don't install laravel/framework v10.0.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.0.3 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.3 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.4 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.5 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.2.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.3.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.3.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.3.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.3.3 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.4.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.4.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.5.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.5.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.6.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.6.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.6.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.7.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.7.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.8.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.9.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.10.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.10.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.11.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.12.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.3 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.5 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.0.1 (conflict analysis result)
    - fruitcake/laravel-cors v2.0.0 requires illuminate/support ^5.6|^6.0|^7.0|^8.0 -> satisfiable by illuminate/support[v5.6.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27].
    - Only one of these can be installed: illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.9, v10.0.0, ..., v10.13.5], laravel/framework[v10.0.0, ..., v10.13.5]. laravel/framework replaces illuminate/support and thus cannot coexist with it.
    - Root composer.json requires laravel/framework ^10.0 -> satisfiable by laravel/framework[v10.0.0, ..., v10.13.5].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

On the github page there is a docker option but I didn't manage to make it work. Either methods are fine by me.

0 likes
6 replies
Snapey's avatar

you should composer install, not upgrade ?

neon_beam's avatar

I tried that, same result: composer install with composer.lock file

Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.
- Required package "laravel/framework" is in the lock file as "v9.44.0" but that does not satisfy your constraint "^10.0".
- Required (in require-dev) package "nunomaduro/collision" is in the lock file as "v6.3.1" but that does not satisfy your constraint "^7.0".
- Required (in require-dev) package "phpunit/phpunit" is in the lock file as "9.5.27" but that does not satisfy your constraint "^10.0".
- Required (in require-dev) package "spatie/laravel-ignition" is in the lock file as "1.6.2" but that does not satisfy your constraint "^2.0".
This usually happens when composer files are incorrectly merged or the composer.json file is manually edited.
Read more about correctly resolving merge conflicts https://getcomposer.org/doc/articles/resolving-merge-conflicts.md
and prefer using the "require" command over editing the composer.json file directly https://getcomposer.org/doc/03-cli.md#require-r

After deleting the composer.lock file:

No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install fruitcake/laravel-cors v2.0.1 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.0.2 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.0.4 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.0.5 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.1.0 (conflict analysis result)
    - Conclusion: don't install fruitcake/laravel-cors v2.2.0 (conflict analysis result)
    - illuminate/support[v5.6.0, ..., v5.8.36] require php ^7.1.3 -> your php version (8.2.7) does not satisfy that requirement.
    - illuminate/support[v6.0.0, ..., v6.19.1] require php ^7.2 -> your php version (8.2.7) does not satisfy that requirement.
    - illuminate/support[v7.0.0, ..., v7.28.4] require php ^7.2.5 -> your php version (8.2.7) does not satisfy that requirement.
    - illuminate/support[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.2.7) does not satisfy that requirement.
    - Root composer.json requires fruitcake/laravel-cors ^2.0 -> satisfiable by fruitcake/laravel-cors[v2.0.0, ..., v2.2.0].
    - Conclusion: don't install laravel/framework v10.0.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.0.3 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.3 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.4 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.1.5 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.2.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.3.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.3.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.3.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.3.3 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.4.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.4.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.5.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.5.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.6.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.6.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.6.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.7.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.7.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.8.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.9.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.10.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.10.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.11.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.12.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.0 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.1 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.2 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.3 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.13.5 (conflict analysis result)
    - Conclusion: don't install laravel/framework v10.0.1 (conflict analysis result)
    - fruitcake/laravel-cors v2.0.0 requires illuminate/support ^5.6|^6.0|^7.0|^8.0 -> satisfiable by illuminate/support[v5.6.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27].
    - Only one of these can be installed: illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.9, v10.0.0, ..., v10.13.5], laravel/framework[v10.0.0, ..., v10.13.5]. laravel/framework replaces illuminate/support and thus cannot coexist with it.
    - Root composer.json requires laravel/framework ^10.0 -> satisfiable by laravel/framework[v10.0.0, ..., v10.13.5].
neon_beam's avatar

Still the same kind of errors after removing "fruitcake/laravel-cors": "^2.0" and deleting the composer.lock file.

villamarianne's avatar

This post is a little bit old, maybe the author updated the package in the meantime. I guess the problem was, that your PHP version (8.2) was to new for some dependencies.

I just tried to run that package and composer update or composer install worked perfectly. I was using PHP 8.2

Please or to participate in this conversation.