Hello. Now again cant install or update project.
yiisoft/yii2 2.0.10 requires bower-asset/jquery 2.2.*@stable | 2.1.*@stable | 1.11.*@stable | 1.12.*@stable -no matching package found.
fxp/composer-asset-plugin version is 1.2.2
what is the command you are running and what is the complete output?
composer create-project --prefer-dist yiisoft/yii2-app-basic delete_me3
You are running Composer with SSL/TLS protection disabled.
Warning: Accessing packagist.org over http which is an insecure protocol.
Installing yiisoft/yii2-app-basic (2.0.10)
Problem 1
- yiisoft/yii2 2.0.9 requires bower-asset/jquery 2.2.@stable | 2.1.@stable | 1.11.@stable | 1.12.@stable -> no matching package found.
- yiisoft/yii2 2.0.8 requires bower-asset/jquery 2.2.@stable | 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.7 requires bower-asset/jquery 2.2.@stable | 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.6 requires bower-asset/jquery 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.5 requires bower-asset/jquery 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.10 requires bower-asset/jquery 2.2.@stable | 2.1.@stable | 1.11.@stable | 1.12.@stable -> no matching package found.
- yiisoft/yii2 2.0.9 requires bower-asset/jquery 2.2.@stable | 2.1.@stable | 1.11.@stable | 1.12.@stable -> no matching package found.
- yiisoft/yii2 2.0.8 requires bower-asset/jquery 2.2.@stable | 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.7 requires bower-asset/jquery 2.2.@stable | 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.6 requires bower-asset/jquery 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.5 requires bower-asset/jquery 2.1.@stable | 1.11.@stable -> no matching package found.
- yiisoft/yii2 2.0.10 requires bower-asset/jquery 2.2.@stable | 2.1.@stable | 1.11.@stable | 1.12.@stable -> no matching package found.
- Installation request for yiisoft/yii2 ~2.0.5 -> satisfiable by yiisoft/yii2[2.0.10, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9].
Potential causes:
Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.
Show result of composer global show
.
composer global show
Changed current directory to C:/Users/myzajtse/AppData/Roaming/Composer
You are running Composer with SSL/TLS protection disabled.
fxp/composer-asset-plugin v1.2.2 NPM/Bower Dependency Manager for Composer
Maybe the network of bower/npm or it's CDN service is unstable, please wait for a while and try again.
Closing since it's not reproducible so we can't fix it.
@earlcherry Did you run the composer global require "fxp/composer-asset-plugin"
to install client assets?
Hey, guys! I am having the same issue right now. Nothing helps. I tried to remove the executable itself with the root and config folders and reinstall the composer. Tried to remove the project I want to deploy and wipe out everything relative to the composer. Still no luck.
The project was successfully deployed on another machine earlier.
Globally only fxp/composer-asset-plugin installed.
I guess the reason is there was an old version of composer, you need to update it or fix the old one by adding the missing plugin: "fxp/composer-asset-plugin" as @davidjeddy says.
No, that was because of broken dependencies. It was quickly fixed.
Here is the thread about this issue #14275
So where are bower assets supposed to be now? vendor/bower-asset
or vendor/bower
?
@vercotux Yii 2.0.12 has them in ./vendor/bower
by default.
@davidjeddy I'm using 2.0.12 and it puts them in vendor/bower-asset
.
that does not depend on the Yii version but on the configuration in application template. You can configure it yourself.
@cebe I thought so. I assume it mostly depends on the fxp/composer-asset-plugin
version which configures your project when you run composer create-project
. I reckon it calls some composer-triggered scripts? Is there any way to re-do that step once we've already created the project (without creating a new project)?
Make sure composer config and application aliases match:
Most helpful comment
@earlcherry Did you run the
composer global require "fxp/composer-asset-plugin"
to install client assets?