Add bower.json about uuid HOT 8 CLOSED

Since you need npm to get bower, why not just skip the middle man, and use npm? You can use the path ./node_modules/uuid/index.js as a point of reference...

I've been leaning the opposite way, to just use npm, and skip bower altogether.

from uuid.

Npm and bower are not working the same way, npm is installing dependencies in sub-directory while bower is installing dependency in the same directory.

When you work on the client, you don't want that line to include jquery:

bower_components/bootstrap/bower_components/jquery/dist/jquery.js

Because if another module needs jQuery, what jQuery version to choose? This is solved by bower resolution.

That's why I use bower for client dependencies.

from uuid.

+1 bower is quite different and is also useful to separate "frontend" stuff from "backend" stuff.

Can you please add it?

from uuid.

Why do you need bower.json?
node-uuid is already available through Bower.

bower info node-uuid

Latest version 1.4.2 is available.

from uuid.

I don't know why there is a debate of adding or not adding a bower.json, bower has a spec, every packages available on bower should have a bower.json. If you don't want to follow this rule I don't care, it was just a suggestion.

from uuid.

Hey gang, sorry for not chiming in earlier. I'm not a Bower user so it's hard for me to opine on the pros and cons of this. But it seems like most other major projects have bower.json support so I'm happy to take a pull request.

from uuid.

hi,

following http://bower.io/docs/creating-packages/ see PR #105

Hope it s fine.

from uuid.

Closed in #105

from uuid.