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
question: Bower support? #289
Comments
We don't use bower routinely for Knight Lab projects, but I feel like every time I look into it, I mostly see warnings that it's dead, or questions about whether it is dead, or suggestions that it should merge with npm... which doesn't motivate me to invest a lot of energy. My read is that we are better off supporting npm (see #308). I'll leave this open for a while to see if anyone wants to champion Bower, but if there's no clear momentum for it in a month or two, we'll close this. |
Many projects are indeed moving from other package managers ( including Bower ) to NPM. I apologize for not being clearer. What I was implying was using ANY package manager. Some open source projects have even gone as far as offering bower AND npm. The setup is very easy and I do not expect that work to fall on the KnightLab team. After all, the project is open source and what better way to say "thank you for your contribution" than pull request? 😄 |
👍 for NPM |
Closing this in favor of #308 |
I'm curious to know what the authors' thoughts are on providing bower support.
The text was updated successfully, but these errors were encountered: