You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just replacing bower with npm might lead to problems, since both services work very differently.
In a nutshell: Bower was actually made in a way how we use it in Yii 2 for (pre-bundled) frontend assets, npm is more meant to be build with ie. webpack, although most packages have dist files, but it's not required. Also the dependencies may vary a lot.
I'd strongly recommend to wait for a fix in asset-packagist.
@bizley@terabytesoftw A change from bower to npm might be an option for 2.2, but please not for 2.0.
Related f.ex. to hiqdev/asset-packagist#163 and especially to hiqdev/asset-packagist#163 (comment) .
composer update
results to some packages downgrade.Question is if/how it's related to https://bower.io/, it (as stated there) is maintained, but f.ex.
All packages required by Yii2 are available as
npm-asset/package
and versions seem to be correct in that case.The text was updated successfully, but these errors were encountered: