search

angular / angular-hint

run-time hinting for AngularJS applications
362 stars 45 forks source link

(chore): Add bower definition and dist files #45

Closed joscha closed 9 years ago

joscha commented 9 years ago

Our project only exposes bower components to the web and not npm modules. As I would like to depend upon angular-hint without adding an extra build step, a bower component would be the easiest way to manage this dependency. Therefore I propose to expose the browserified hint.js via bower package. As I am not sure whether this should be happening in a separate repositiory instead and/or if anyone agrees this is a general use-case, I am opening this PR for general discussion.

mgol commented 9 years ago

I don't think that's the right approach. We'd have to generate built files in every commit which would bump repo size significantly. A way to do it is to only generate those files for releases and put them in detached commits but that creates a maintenance burden.

Because of that and because npm is going to slowly replace bower, I think a bower package for this should be managed in a separate repository.

That's up to @btford, though.

simplesmiler commented 9 years ago

+1 for separate repository.

joscha commented 9 years ago

I hear you - a separate repo would also allow for more easy (automatic) bumping of versions separately from the component itself and limit the clutter in the "ignore" section of bower.json. @btford, what do you thin? Should I just go ahead and create such a repo or do you think it should be under the "angular" github hat?

stevemao commented 9 years ago

+1 @mzgol , this is the usual way that angular does. Also need to add gulp tasks to bump version, push to bower repos and cdn etc.

SomeKittens commented 9 years ago

Angular is moving away from Bower and toward NPM. Sorry folks.