Please publish to npm
Closed this issue · 11 comments
npm is a popular package manager for js. If you publish this module there, it will allow it to be consumed via browserify. All you need to do is add a name and version to package.json and run npm publish in this repo.
It kind of feels strange for me to publish a browser module to NPM. What is the current trend in this? Is 'everyone' doing this?
Don't do it, bower is fine.
It kind of feels strange for me to publish a browser module to NPM.
It's not strange at all! There's no reason that npm needs to only contain node modules. Almost everything on npm is a browser module anyway by the magic of browserify.
Is 'everyone' doing this?
Yes, pretty much. Angular itself is working towards publishing on npm.
Don't do it, bower is fine.
I can't tell if you're 
ing haha. Bower is not fine for many use cases. Why would you insist that everyone use the same package manager?
Why would you insist that everyone use the same package manager?
From the guy who wants everything to live inside npm and then uses
Bower is far from perfect, same with npm. Just when you do it this way you're forcing people into a style and process they may not be willing to adopt. Bower just puts things in a far looser set up so people don't have to spend half a day changing maven, grunt or bash etc.
Best thing would be to do both 👻
Bower is far from perfect, same with npm.
Totally agree.
Best thing would be to do both
Absolutely! Nothing about supporting one of these package managers precludes supporting the other.
immature insult removed
@MaxSvargal +1
@MaxSvargal mature and welcoming.
I'd love to see this package on NPM. As Angular is published on NPM too, I'd prefer to keep a single package manager instead of installing bower just for one lib.
So a big +1 for it. :)
+1. Working with angular all my dependencies come thru npm. I used to use bower, but we had so many problems with it that we eventually only used it for setting up our project,then we committed all the packages to our project repository so they would be available for every build rather than using bower to download them on every build. (The build used to break randomly when bower had a panic attack).
I any case, the angular team has migrated to using npm over bower; angular-ui-router is available on npm now, so it makes sense to have the ui-router.stateHelper available on npm as well to keep all dependencies together.
Currently I am forced to use bower to download stateHelper, which then downloads copies of angular and angular-ui-router from bower. so now I have 2 copies of the angular dependencies, one in bower_components and one in node_modules... not very efficient.
Please update the package.json and run npm publish... thank you.