Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get rid of the Bower package manager #20

Open
tanius opened this issue Oct 22, 2019 · 0 comments
Open

Get rid of the Bower package manager #20

tanius opened this issue Oct 22, 2019 · 0 comments

Comments

@tanius
Copy link
Member

tanius commented Oct 22, 2019

The current installation instructions in README.md instruct to install both bower and npm. That's a redundancy in the build environment that can be simplified by just using npm. If some packages are only available via bower, then we'd have to convert them to npm packages ourselves.

It just does not seem that Bower adds any major feature over NPM that would justify its use, much less using it in parallel with NPM for a small software like this.

Moreover, when installing Bower (sudo npm install -g bower), it even tells that it is now deprecated:

WARN deprecated [email protected]: We don't recommend using Bower for new projects. 
Please consider Yarn and Webpack or Parcel. You can read how to migrate 
legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

So it seems it's time to modernize that part of the build environment …

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant