-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Require composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint. #8913
Comments
Well, the plugin ecosystem is not yet fully compatible with the upcoming Composer 2.0. There is #8726 to track this |
@stof thanks! |
I've install composer 1.4.1 , with this worked for me. |
Use this command to downgrade composer to 1.0 |
At this time, running |
Still not working, though composer 2 is now a default version |
Multiple projects use different versions of packages and composer-plugin-api as a result.
AFter trying to require package for older project got this error
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
composer install / update --no-plugins
composer self-update
makes no sense because some of the packages are outdated and it is installed globally.composer update --with-all-dependencies
also gives not results.Composer lock in older projects has requirements for plugin-api v 1.0 only.
The only suitable solution I see is installing different versions of the composer per project.
Of course, downgrading is also an option
composer self-update 1.*.*
but newer projects may suffer :)My
composer.json
:Output of
composer diagnose
:When I run this command:
I get the following output:
Removing vendors folder and composer.lock, then
And I expected this to happen:
Packages are updated or installed.
Is there other than mentioned solutions?
The text was updated successfully, but these errors were encountered: