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 #37

Open
mateusdemboski opened this issue Oct 16, 2015 · 19 comments
Open

Bower #37

mateusdemboski opened this issue Oct 16, 2015 · 19 comments
Labels

Comments

@mateusdemboski
Copy link

Hi! could be added in the project a bower.json to facilitate the maintenance of "front-end" dependencies. =)

tks,

@developit
Copy link
Contributor

People still use Bower?

@developit
Copy link
Contributor

I was going to suggest NPM since it's already available there, no need to take offence.

@schnti
Copy link

schnti commented Oct 16, 2015

+1

@sbruchmann
Copy link

@developit FYI, you can already install Photon via npm by using its repository url:

npm install https://github.com/connors/photon

@developit
Copy link
Contributor

@sbruchmann indeed, or even npm i connors/photon :). It's a pity the photon name is already taken in NPM though :(

@knownasilya
Copy link

What about namespaced? npm i @connors/photon

@developit
Copy link
Contributor

@knownasilya yeah, that'd work (as long as nobody is trying to install with npm older than 2.x).

@knownasilya
Copy link

In that case, it might be worth mentioning the version of npm required.

@knownasilya
Copy link

Or it could be published as photonkit.

@developit
Copy link
Contributor

^ nice, that would actually address #36, too ;)

@neodon
Copy link

neodon commented Oct 19, 2015

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. :)

@dbpolito
Copy link

👍 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...

@wong2
Copy link

wong2 commented Nov 12, 2015

photonkit is a nice name

@dbpolito
Copy link

indeed, keep the same name across is good, github, npm, site...

@mateusdemboski
Copy link
Author

+1 about keep the same name across and using photonkit, now used only on site, is possible registry the package on bower and npm...

@pedzed
Copy link

pedzed commented Oct 9, 2016

To @sbruchmann and @gligoran: what is your problem? You can provide a bower.json along with a published package.json. I am not sure why you are actively downvoting people wanting Bower support.

@sbruchmann
Copy link

@pedzed I wasn’t voting against bower but against the +1-statement of @frankhale since GitHub now supports reactions to comments.

@gligoran
Copy link

gligoran commented Oct 9, 2016

@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.

@pedzed
Copy link

pedzed commented Oct 9, 2016

@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 bower.json file.

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

No branches or pull requests