We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be great to have a bower.json (define a package) in the repo for bower support and also register it in the collection of repos.
bower.json
This avoids to clone the whole keymaster repo as dependency in bower (which is highly discussed here).
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
I won't add support for packaging system that need me to keep a file in the repo. It's just too invasive.
cool
No branches or pull requests
It would be great to have a
bower.json
(define a package) in the repo for bower support and also register it in the collection of repos.This avoids to clone the whole keymaster repo as dependency in bower (which is highly discussed here).
The text was updated successfully, but these errors were encountered: