-
-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version problem in composer for clean Laravel 9. #561
Comments
Yeah, I got the same on an upgraded installation instead of a clean one. |
Yes, there is an issue with dependencies. But you can fix it with |
Hi @50bhan . I have try it but without any success:
|
@divoto It's odd! Because I was able to install the package on a clean L9. |
What version of PHP. Mine is 8.0 |
Hi @50bhan |
Hi, I think that I have a connected issue. I managed to install phpinsights, but when I run
This is my
I tried deleting |
fixed in #566 |
The problem is not solved @cmgmyr Problem 1 |
On clean Laravel 9 i get error when using composer require:
`composer require nunomaduro/phpinsights --dev
Using version ^2.1 for nunomaduro/phpinsights
./composer.json has been updated
Running composer update nunomaduro/phpinsights
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 nunomaduro/phpinsights ^2.1 -> satisfiable by nunomaduro/phpinsights[v2.1.0].
- nunomaduro/phpinsights v2.1.0 requires psr/simple-cache ^1.0 -> found psr/simple-cache[1.0.0, 1.0.1] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
`
Again problem with psr/simple-cache.
Thank you.
The text was updated successfully, but these errors were encountered: