-
Notifications
You must be signed in to change notification settings - Fork 579
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 #37
Comments
People still use Bower? |
I was going to suggest NPM since it's already available there, no need to take offence. |
+1 |
@developit FYI, you can already install Photon via npm by using its repository url: npm install https://github.com/connors/photon |
@sbruchmann indeed, or even |
What about namespaced? |
@knownasilya yeah, that'd work (as long as nobody is trying to install with npm older than 2.x). |
In that case, it might be worth mentioning the version of npm required. |
Or it could be published as |
^ nice, that would actually address #36, too ;) |
I accidentally installed the other photon package with npm and was really confused at first. Figured out how to add this one with the git url though. Publishing it on npm (and possibly bower), even under a slightly different name, would be cool. :) |
👍 for npm support... i know it's easy to use github url, but i think being at npm main repo it would also help the project popularity... |
|
indeed, keep the same name across is good, github, npm, site... |
+1 about keep the same name across and using |
To @sbruchmann and @gligoran: what is your problem? You can provide a |
@pedzed I wasn’t voting against |
@pedzed Wasn't actually downvoting people for wanting bower support, but the manner in which @a3bhea commented. This is supposed to be a place where people work together, so no need to be condescending. |
@sbruchmann I agree, people should not spam with +1's. But it's like slapping a child for doing something wrong: the child does not know what it did wrong, you have to explain. On the other hand, I understand that you don't want to add another comment just to say that. @gligoran I apologize if that's the case. The reason I mentioned you was because you downvoted two or three other comments talking about Bower. I'm currently using #37 (comment) suggestion, but it would be nice if it was registered as an NPM/Bower package of course (preferably both). If wanted, I'll even provide a |
Hi! could be added in the project a bower.json to facilitate the maintenance of "front-end" dependencies. =)
tks,
The text was updated successfully, but these errors were encountered: