our requirements could not be resolved to an installable set of packages.
Problem 1
- botman/studio-addons[1.3.0, ..., 1.6.1] require thecodingmachine/discovery ^1.2 -> satisfiable by thecodingmachine/discovery[v1.2.0, v1.2.1].
- thecodingmachine/discovery[v1.2.0, ..., v1.2.1] require composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
- Root composer.json requires botman/studio-addons ~1.3 -> satisfiable by botman/studio-addons[1.3.0, ..., 1.6.1].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.
Same problem
The discovery package seems incompatible with Composer 2.0, so try these steps:
composer upgrade to update to the most recent version, if that failscomposer upgrade but remove vendor and composer.lock first, if that fails toocomposer self-update --1) to resolve it for now (it doesn't solve the problem, though). The discovery package is incompatible with Composer 2.0, downgrade Composer to 1.0 (
composer self-update --1) to resolve it for now (it doesn't solve the problem, though).As the discovery package hasn't been updated in 4 years, I'm afraid we'll have to look for a different solution (maybe something like how Laravel discovers packages?)
After downgrading to composer v1, it works.
Thank you.
Looks like this is not a composer issue. I also encounted some issue. Can you try these steps after you have run composer create-project?
composer upgradeThis worked for me, also with Composer 2.0
Looks like this is not a composer issue. I also encounted some issue. Can you try these steps after you have run
composer create-project?* Run `composer upgrade`This worked for me, also with Composer 2.0
Yeah, it works.
Thank you.
Most helpful comment
The discovery package seems incompatible with Composer 2.0, so try these steps:
composer upgradeto update to the most recent version, if that failscomposer upgradebut removevendorandcomposer.lockfirst, if that fails toocomposer self-update --1) to resolve it for now (it doesn't solve the problem, though).