Open donalhenry opened 6 years ago
I don't think adding bower support is a good idea. Bower is a deprecated tool https://bower.io/blog/2017/how-to-migrate-away-from-bower/.
I've used https://github.com/sheerun/bower-away on a big AngularJS project using bower and it had worked very well.
Whilst bower-away
converts dependencies to yarn quite nicely, it doesn't handle things like wiredep that you might have in your gruntfile for instance.
Using npm to install bower as per here hasn't been 100% reliable.
OK. Thanks for the advice. This is a small app so I think I will convert it to yarn or grunt.
I'm a big user of this plugin, and today encountered one of our node applications that uses bower.
Any reason why this plugin couldn't be extended to use bower. Seems like its relationship to npm is the same as grunt, so the support within the code would be similar.
Make sense?