Composer "Your requirements could not be resolved to an installable set of packages": how to read and fix it

Composer "Your requirements could not be resolved to an installable set of packages": how to read and fix it

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Few PHP developers have escaped Your requirements could not be resolved to an installable set of packages. The error looks like a wall of text, but it is really a dependency conflict report: Composer is telling you that two or more of your version constraints cannot be true at the same time. Once you read it as a report instead of noise, the fix is usually a one-line change.

Read the error from the bottom up

The last lines of the output are the conclusion; the lines above are the reasoning. A typical failure ends like this:

Problem 1
  - Root composer.json requires laravel/framework ^11.0 -> satisfiable by laravel/framework[v11.0.0, ...].
  - some/package v2.3.0 requires laravel/framework ^10.0 -> found laravel/framework[v10.0.0, ...] but it does not match your constraint.
  - Root composer.json requires some/package ^2.3 -> satisfiable by some/package[v2.3.0].

Translation: your composer.json wants laravel/framework ^11.0 and some/package ^2.3, but some/package 2.3 only works with Laravel 10. No release exists that satisfies both, so there is nothing to install.

The five usual causes

1. A package has no release for your framework or PHP version. The package lags a major Laravel or PHP upgrade. Check its releases for a newer major, or ask Composer directly:

composer why-not laravel/framework 11.0
composer why-not php 8.3

why-not (alias prohibits) lists exactly which installed or required packages block a given version.

2. Your PHP version does not match. Composer resolves against the PHP running the CLI, which is not always the version your site uses. Check with composer show -p | grep '^php ' and php -v. On servers with multiple PHP versions, call the right one explicitly: php8.3 /usr/local/bin/composer update.

3. A missing PHP extension. Requirements like ext-intl or ext-gd are platform packages. If the CLI lacks the extension, resolution fails. Install it (sudo apt install php8.3-intl) or check what is loaded with php -m.

4. Conflicting constraints in your own composer.json. Two direct requirements can disagree, for example "guzzlehttp/guzzle": "^6.0" while a package you added needs Guzzle 7. Loosen the constraint you control.

5. Stability flags. If you require a beta or RC release without setting "minimum-stability" or an inline @beta/@RC flag, Composer pretends those releases do not exist.

Fix it the right way

Update the blocking package to a version that supports your stack, or relax your own constraint. When several packages moved together, let Composer re-resolve the whole tree:

composer update --with-all-dependencies

If you added a package with composer require and it failed, your composer.json may already contain the new line - remove it or adjust the version before retrying.

The escape hatch you should avoid

composer install --ignore-platform-reqs skips PHP and extension checks entirely. It is acceptable inside a Docker build where the runtime image guarantees the platform, but on a real server it installs code your PHP cannot run. Fix the platform, not the check.

Summary

Read the error from the bottom up, run composer why-not on the contested package, and check which PHP and extensions Composer actually sees. The conflict is almost always a real incompatibility - the fix is choosing versions that agree, not forcing the install.

Composer PHP Dependencies Troubleshooting

Our network