Laravel, composer install, don't install laravel/framework
Seeing a composer.json that works in one environment but fails immediately upon cloning and running composer install elsewhere is a classic version control trap. When you encounter the error message "Conclusion: don't install laravel/framework" alongside a long list of rejected versions, it usually points to a fundamental misunderstanding of how dependency resolution handles package aliases and conflicting constraints.
In the scenario where the code works in an office machine but fails at home, the culprit is almost certainly not the PHP version or the OS itself, but rather the specific version of Composer installed on each machine. The error log reveals a critical conflict: the project requires laravel/framework version 5.1.*, while the third-party package orangehill/iseed dev-master depends on illuminate/support ~5.3.8.
Here is the breakdown of why this fails and how to fix it without manually editing the dependency files.
The Version Constraint Mismatch
The core issue lies in the relationship between major versions and minor dependencies. In the Laravel ecosystem, laravel/framework version 5.1.x relies on illuminate/support packages that are roughly compatible with the 5.1 series (e.g., v5.1.*). However, the package orangehill/iseed dev-master has a hard requirement for illuminate/support v5.3.16 or v5.3.23.
Composer's dependency resolver operates on a strict "AND" logic when resolving transitive dependencies. When it attempts to satisfy the request:
- It needs
laravel/framework5.1.x (from yourrequiresection). - It also needs
illuminate/support5.3.x (fromorangehill/iseed).
Because Laravel 5.1 does not include or support illuminate/support 5.3, Composer concludes that no valid state exists where both requirements are met simultaneously. The error message lists every version of laravel/framework it refuses to install because installing any of them would inevitably break the constraint imposed by iseed.
Why It Works in the Office but Fails at Home
The discrepancy between environments often stems from outdated Composer versions. Older versions of Composer might be more lenient with version constraints or may not correctly resolve complex diamond dependencies involving different major patch levels within the same minor branch. If your office machine has a newer version of Composer (e.g., 1.x or later) and your home machine is running an ancient version (perhaps 0.x), the resolver logic differs significantly. The older tool might fail to detect that the two Laravel versions are incompatible, whereas the newer tool correctly identifies the conflict and blocks the installation.
The Solution: Update orangehill/iseed
The most robust fix is to update the problematic package. The package orangehill/iseed was an early iteration of seeding tools for Laravel. Over time, it evolved (and eventually became part of the broader ecosystem or replaced by more maintained alternatives like spatie/laravel-seeder).
If you are maintaining a legacy codebase that strictly requires this specific version of iseed, you must relax the constraint on laravel/framework. You cannot have Laravel 5.1 and Illuminate 5.3 coexisting. You would need to upgrade the entire project to Laravel 5.3 or higher to satisfy iseed's requirements, which involves changing every file in your application.
However, if you simply want the dependencies to install on a fresh machine, the immediate fix is to ensure your environment uses a modern version of Composer. Run:
composer self-update
Once updated, run composer install again. The newer resolver will explicitly fail with a clearer error message explaining that laravel/framework 5.1.* and illuminate/support ^5.3 are incompatible, rather than listing hundreds of "don't install" lines for the framework.
Modernizing the Dependency Graph
If you have control over the project requirements, consider replacing orangehill/iseed with a modern alternative that supports current Laravel versions. This eliminates the version skew entirely. If you are working on a legacy migration, upgrading from Laravel 5.1 to 5.3 is necessary before resolving the dependency graph correctly.
A Note on Legacy Packages
When dealing with packages like orangehill/iseed, always verify if they have been archived or succeeded by more actively maintained libraries. Relying on dev-master branches of unmaintained packages introduces significant risk, as their internal dependencies may drift without warning. If you need a seeding solution today, look for packages that explicitly state compatibility with your target Laravel version rather than relying on implicit version matching that fails across environments.
For complex legacy migrations where dependency resolution becomes a nightmare, consulting specialized resources or hiring an expert can save hours of debugging environment-specific failures. You might find relevant case studies or migration guides at https://laravelcompany.com if you need guidance on modernizing your stack.