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

Bower removal #197

Closed
alexthewilde opened this issue Feb 11, 2017 · 3 comments
Closed

Bower removal #197

alexthewilde opened this issue Feb 11, 2017 · 3 comments

Comments

@alexthewilde
Copy link

Can you explain the reason behind the removal from bower?

I'm actually depending on the bower component, so for me the only way would be to maintain my own fork with a bower.json.

@tambien
Copy link
Contributor

tambien commented Feb 11, 2017

I am always looking for ways to simplify the onboarding of Tone.js, and giving fewer ways to install it seemed helpful. Especially for someone new to programming or javascript, they don't need to go reading about the difference between bower and npm to decide which they should use. It also seems that many other libraries have chosen npm over bower.

Is it possible for you to switch over to npm?

I am fine with adding bower.json back if npm is not an alternative for you and other users.

@alexthewilde
Copy link
Author

Thanks for clarifying. I get your point, although I think that bower is still a very common install option.

My own build process is using bower components exclusively and I'd prefer to keep it that simple if possible.

@alexthewilde
Copy link
Author

@tambien thanks!!

tambien added a commit that referenced this issue Dec 6, 2019
Anyone still need bower.json?

addresses #197
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

2 participants