Could I not update all the packages from bower when i only want update single composer package

[sevenT]

Could I not update all the packages from bower when i only want update single composer package ?

[francoispluchino]

Alas no, Composer retrieves a complete list of all packages. This is the native behavior of Composer.

[cebe]

composer update myvendor/mypackage ?

[francoispluchino]

Yes, in internal, Composer retrieves always all package definitions... even for a single package. In view of the previous discussions, I do not think it will change quickly.

[SDKiller]

Composer retrieves always all package definitions... even for a single package.

Confirm, had the similar issue.

I do not think it will change quickly

@francoispluchino

May be offtopic, but related to #93 and many composer issues not solved and nice-to-have proposals still not implemented - don't you think it's time to fork composer ? ;-)

[sevenT]

@cebe that's exact what i did to update my local package.
@francoispluchino Thanks for this awesome project.
It seems a composer problem. The awful internet of CHN really drive me crazy.

[cebe]

@sevenT there is a local composer cache, when you use that you might need to download each package only once: https://toranproxy.com/
Not sure if it plays well with this plugin though.

[sevenT]

Thanks @cebe we've build up a local cache with satis, but only for php package. It still try to download extra asset packages. Maybe I should try to cache bower packages as well, I'll try this later when i got time and getting more familiar with how all these things work. Many Thanks

[dynasource]

Im a really heavy use of "composer update myvendor/mypackage" but this isnt possible anymore since using the composer-asset-plugin + bower declarions in composer.json. It is still supported by composer (see composer/composer#450)

My question is, is this issue solved by #93?

[francoispluchino]

@dynasource This could be fixed by this issue.

[dynasource]

Excellent. Whats left to do to benefit from your patch?
thanks

[francoispluchino]

I must develop the new version 2.0 that used Nodejs. So for the moment this is not available.

[francoispluchino]

@nsams It is also a solution.