Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hi all,
I'm tryin to upgrade to laravel v10 from 9. I ran composer update but i have this error:
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires renatomarinho/laravel-page-speed ^3.0, found renatomarinho/laravel-page-speed[dev-master, 1.0.0, ..., 1.9.0, 2.0.0, 2.1.0] but it does not match the constraint.
Problem 2
- Root composer.json requires realrashid/sweet-alert ^5.1 -> satisfiable by realrashid/sweet-alert[v5.1.0].
- realrashid/sweet-alert v5.1.0 requires laravel/framework ^5.6|^6.0|^7.0|^8.0|^9.0|^9.11|9.14.* -> found laravel/framework[v5.6.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but it conflicts with your root composer.json require (^10.0).
Problem 3
- Conclusion: don't install fideloper/proxy 4.4.2 (conflict analysis result)
- illuminate/contracts[v5.8.0, ..., 5.8.x-dev] require php ^7.1.3 -> your php version (8.2.12) does not satisfy that requirement.
- illuminate/contracts[v6.0.0, ..., v6.19.1] require php ^7.2 -> your php version (8.2.12) does not satisfy that requirement.
- illuminate/contracts[v7.0.0, ..., v7.28.4] require php ^7.2.5 -> your php version (8.2.12) does not satisfy that requirement.
- illuminate/contracts[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.2.12) does not satisfy that requirement.
- Root composer.json requires fideloper/proxy ^4.4 -> satisfiable by fideloper/proxy[4.4.0, 4.4.1, 4.4.2].
- Conclusion: don't install laravel/framework v10.0.1 (conflict analysis result)
- 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.14.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.14.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.15.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.16.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.16.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.17.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.17.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.18.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.19.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.20.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.21.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.21.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.22.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.23.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.23.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.24.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.25.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.25.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.25.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.26.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.26.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.26.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.27.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.28.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.29.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.30.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.30.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.31.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.32.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.32.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.33.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.34.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.35.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.36.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.37.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.38.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.39.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.40.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.41.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.42.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.43.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.44.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.45.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.45.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.46.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.47.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.0 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.1 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.2 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.3 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.4 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.5 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.6 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.7 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.8 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.9 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.10 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.11 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.12 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.13 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.14 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.15 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.16 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.17 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.18 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.48.19 (conflict analysis result)
- Conclusion: don't install laravel/framework v10.0.0 (conflict analysis result)
- fideloper/proxy 4.4.0 requires illuminate/contracts ^5.0|^6.0|^7.0|^8.0 -> satisfiable by illuminate/contracts[v5.0.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev].
- Only one of these can be installed: illuminate/contracts[v5.0.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev, v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev], laravel/framework[v10.0.0, ..., 10.x-dev]. laravel/framework replaces illuminate/contracts and thus cannot coexist with it.
- Root composer.json requires laravel/framework ^10.0 -> satisfiable by laravel/framework[v10.0.0, ..., 10.x-dev].
Here is composer.json file
{
"name": "laravel/laravel",
"type": "project",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"require": {
"php": "^8.2",
"fideloper/proxy": "^4.4",
"guzzlehttp/guzzle": "^7.0.1",
"hashids/hashids": "^4.1",
"intervention/image": "^2.5",
"jenssegers/date": "^4.0",
"jorenvanhocht/laravel-share": "^4.0",
"laravel/framework": "^10.0",
"laravel/tinker": "^2.5",
"laravel/ui": "^4.0",
"livewire/livewire": "^2.5",
"mcamara/laravel-localization": "^1.6",
"mews/purifier": "^3.3",
"realrashid/sweet-alert": "^5.1",
"renatomarinho/laravel-page-speed": "^3.0",
"spatie/laravel-translatable": "^6.0"
},
"require-dev": {
"barryvdh/laravel-debugbar": "^3.6",
"spatie/laravel-ignition": "^2.0",
"fakerphp/faker": "^1.13",
"laravel/sail": "^1.26",
"mockery/mockery": "^1.6",
"nunomaduro/collision": "^7.0",
"phpunit/phpunit": "^11.0.1"
},
"autoload": {
"psr-4": {
"App\": "app/",
"Database\Factories\": "database/factories/",
"Database\Seeders\": "database/seeders/"
},
"files": [
"app/Helpers/General.php"
]
},
"autoload-dev": {
"psr-4": {
"Tests\": "tests/"
}
},
"scripts": {
"post-autoload-dump": [
"Illuminate\Foundation\ComposerScripts::postAutoloadDump",
"@php artisan package:discover --ansi"
],
"post-root-package-install": [
"@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
],
"post-create-project-cmd": [
"@php artisan key:generate --ansi"
]
},
"extra": {
"laravel": {
"dont-discover": []
}
},
"config": {
"optimize-autoloader": true,
"preferred-install": "dist",
"sort-packages": true
},
"minimum-stability": "dev",
"prefer-stable": true
}
Also tried to remove the dependencies that are causing the issue from the composer.json to see it works but still the same. I appreciate your support.
Did you manually update laravel first?
https://laravel.com/docs/10.x/upgrade
Like the answers after mine, the upgrade guide clearly states to check your dependencies. That means dependency requirements.
I.e. can this package work with the version of laravel I am now using.
This is always the answer to these composer error questions. The upgrade guide even shows what version of composer is required.
@jlrdw Thanks for your support! No, i changed the file accoridng to the upgrade guide, then tried to composer update. the composer version i installed is 2.7 since it requries 2.2 or greater, but i downgrade to 2.2 just to see if its happy with this version.
@zoul You need to read the error message.
The problem line is this one:
Problem 2
- Root composer.json requires realrashid/sweet-alert ^5.1 -> satisfiable by realrashid/sweet-alert[v5.1.0].
- realrashid/sweet-alert v5.1.0 requires laravel/framework ^5.6|^6.0|^7.0|^8.0|^9.0|^9.11|9.14.* -> found laravel/framework[v5.6.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but it conflicts with your root composer.json require (^10.0).
You're trying to install version 5.1.0 of realrashid/sweet-alert but it is not compatible with Laravel 10.x. So you need to update the version constraint of that package to a version that does support Laravel 10.x.
thanks for your help @martinbean I found the supported realrashid/sweet-alert version for laravel 10.x is 6.0.0 — 7.2.0, changed it to v6.0.0 but still getting error
The fideloper/proxy package is obsolete and is no longer maintained because it has been integrated into Laravel. This has been mentioned in the Laravel upgrade guide. Read this.
Other error messages tell you where the conflicts are:
You're using an old version of realrashid/sweet-alert which isn't compatible with Laravel 10. Upgrade to a newer version.
You're requiring renatomarinho/laravel-page-speed version ^3.0, but that version doesn't seem to exist. The newest published version in packagist is 2.1, and it doesn't support Laravel 10.
Other than that, follow the upgrade guide.
Take first problem, tag ^3.0 for laravel-page-speed, check the tags https://github.com/renatomarinho/laravel-page-speed/tags latest tag is 2.1.0
second problem, update realrashid/sweet-alert to ^6.0
fideloper/proxy this project does not support Laravel 10.
Also tried to remove the dependencies that are causing the issue from the composer.json to see it works but still the same
remove also the composer.lock file ( only if you want to test ), when you run composer install and there's a composer.lock file - then it will be used.
thanks @Sergiu17 for your help.
I changed sweet-alert version to 6.0 and removed composer.lock file, the error i;'m getting is :
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
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- illuminate/support[v6.0.0, ..., v6.19.1] require php ^7.2 -> your php version (8.2.12) does not satisfy that requirement.
- illuminate/support[v7.0.0, ..., v7.28.4] require php ^7.2.5 -> your php version (8.2.12) does not satisfy that requirement.
- illuminate/support[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.2.12) does not satisfy that requirement.
- Root composer.json requires renatomarinho/laravel-page-speed ^2.1.0 -> satisfiable by renatomarinho/laravel-page-speed[2.1.0].
- Conclusion: don't install laravel/framework v10.0.1 (conflict analysis result)
- renatomarinho/laravel-page-speed 2.1.0 requires illuminate/support ^6.0 || ^7.0 || ^8.0 || ^9.0 -> satisfiable by illuminate/support[v6.0.0,
..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev].
- Only one of these can be installed: illuminate/support[v5.8.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev, v10.0.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev], laravel/framework[v10.0.0, ..., 10.x-dev]. 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, ..., 10.x-dev].
@Zoul C’mon, man. Read the error. I told you why you got the error in my previous comment. Maybe apply that logic…?
You’re going to need to repeat the process until you get a set of compatible packages. If you resolve one but then get an error about another package being incompatible, then look at the versions of that package for one that’s compatible with Laravel 10.
Instead of asking questions one by one, check the package's GitHub yourself. This is a task you will do every time you upgrade Laravel, so be sure to remember it.
All Laravel users do this.
@puklipo +1
All Laravel users do this.
I wish I could like 10 times.
@zoul what @puklipo said is exactly what the documentation means by checking packages. Yes you have to manually check yourself and manually update the composer.json file.
The easiest way is start a new project, migrate your MVC over and just pull in packages.
Myself I don't use external packages unless necessary.
Many thanks all of you for your help. Following your tips i could upgrade to laravel 10. will follow the same guide in the future.
Please or to participate in this conversation.