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 support #1

Open
robertmain opened this issue Jan 8, 2015 · 2 comments
Open

Bower support #1

robertmain opened this issue Jan 8, 2015 · 2 comments

Comments

@robertmain
Copy link

It would be kinda nice if this was available on bower (my asset pipeline is bower based) so I could just add it to my bower.json and have it installed for me

@dandv
Copy link
Contributor

dandv commented Jun 25, 2015

@robertmain
Copy link
Author

Because bower is designed to contain front end packages, whereas npm is more for things like express and server side stuff.

I would also like to draw your attention to a point which was mentioned in the article:

"Have you seen the way NPM handles its dependencies? The whole infinite sub-folder nesting is atrocious, especially if you are a Windows user, you are going to love the path issues you will run into because nested dependencies can sometimes exceed the 255 character path limit."

On 25 Jun 2015 3:55 am, "Dan Dascalescu" notifications@github.com wrote:

How about npm? See https://www.quora.com/Why-use-Bower-when-there-is-npm


Reply to this email directly or view it on GitHub
#1 (comment)
.

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