Switch to NPM and drop Bower?
Opened this issue · 5 comments
The second issue is exactly the reason why not to do this. It's already changed in bootstrap4 package to npm, if you have a dependency chain, where you need both (bs4 & bs5), the asset packages conflict each other.
I'm tired to "fetch updates from Bower" manually every-time 😫
At the moment the latest release is 5.3.3: npm-asset/bootstrap, which is match with Bootstrap's latest release.
(The latest one for bower-asset/bootstrap is still v5.3.0-alpha1)
Why not implement something like this in BootstrapAssets and BootstrapPluginAsset?
$this->sourcePath = $this->useNpm ? '@npm/bootstrap' : '@bower/bootstrap';
What about the possibility of choose your poison?
Different asset classes for bower and npm and move the npm-asset/bootstrap respectively the bower-asset/bootstrap to the suggest section of composer.json? Would that be a solution that can all live with?