angular-media-player as npm module about angular-media-player

[colthreepv]

Sorry i miss the point in that, I never used browserify, but seems a tool to use backend-based libraries in frontend (browser), not vice-versa.

Anyway for easy download and version management you can use bower, as it is like NPM, but for frontend libraries

[peterschmidler]

My current workflow is based on npm for the frontend end backend, either with a node.js middleware or with a build system like gulp.js. I'm hesitating to introduce a secondary package manager like bower, so I would use angular-media-player via browserify's require(). If angular-media-player was on npm, I could easily install it via my package.json with npm install. It's very easy to get your module on npm e.g. https://gist.github.com/coolaj86/1318304

[colthreepv]

I've already published modules on npm, but it would require effort maintaining it, and seriously there are not enough users for that I think; I actually miss the point publishing a front-end only library to a node.js module package manager. (big frontend libraries do that probably because of browserify, and headless browsers but amp is just a tiny project compared to them)

Anyway, there are (luckily) alternative solutions:

• napa let's you install arbitrary packages like bower does, but directly from package.json seems best compromise ever
• grunt build script + grunt-bower module (still bower, but automatized)