Issue title: Publish on NPM
 Issue body: Greetings! Would you mind publishing on NPM as well as Bower? Seems like most of the front-end JS community is being driven in this direction. [Angular](http://angularjs.blogspot.com/2015/02/new-angularjs-releases-140-beta5-and.html) and [jQuery](http://blog.npmjs.org/post/111475741445/publishing-your-jquery-plugin-to-npm-the-quick) projects are now being published (or will be published) to NPM.

Moving forward, it's making sense to use Bower less and more of a NPM + Browserify type of workflow. Thank you!

 Comments: 
 Comment 0: Yes, I'm planning to do this, since it seems that NPM is the future.

I don't have a date yet for this, now I'm pretty busy with a huge update for Videogular 1.1.0 that will have cue points. I'm so excited with this new release, you guys are going to love cue points! :D

 Comment 1: Thank you! For anyone else looking for this, until the packages are published to NPM you can install via the github url like: `npm i 2fdevs/bower-videogular`.

Have you considered publishing the CSS too?
 Comment 2: Yes, we have separated repositories for Videogular core, the plugins and the themes. Take a look here:

https://github.com/2fdevs?tab=repositories
 Comment 3: Not quite sure that will actually work.

As far as I can tell, if I want multiple packages (installed via NPM), I would do something like this:

``` shell
npm i 2fdevs/bower-videogular --save
npm i 2fdevs/bower-videogular-overlay-play --save
```

Because the name in both package.json files is "videogular," npm isn't picking up the packages as separate, and is just replacing the contents of `node_modules/videogular` whenever additional packages are installed.

I think the solution is an easy one, just edit the package.json files for each of the bower builds to have separate, descriptive names.

 Comment 4: I've fixed the bower repositories, just tell me if it works.
 Comment 5: @2fdevs It works, files are ending up in different folders.

 Comment 6: Thanks @xErik for testing :)

Closing issue.
 Comment 7: We've published on NPM at the end.

https://www.npmjs.com/package/videogular

`npm install videogular`
 Comment 8: It seems as if the videogular module is not properly exported?
I'm not able to use this with my Browserify setup.
The 'main' file in package.json is the gruntfile.
 Comment 9: I will change it un the next release

 Comment 10: It would also be really awesome to export the name of the modules as well so they can be imported and listed in an app's array of required modules all in one go, like so:

```js
angular.modules('myApp', [
  require('videogular')
])
```

You can see how this was done in [Angular Route](https://www.npmjs.com/package/angular-route) or any of the other angular sub-modules.
 Comment 11: Sorry if I sound spoiled, but is there any ETA on this issue or the next release?

 Comment 12: No problem, I understand :)

I want to do a release this next weekend with a few small fixes.
 Comment 13: Fixed.

Added all plugins on NPM and added support for browserify.

I've created an example repository: https://github.com/2fdevs/videogular-browserify

See the changelog to see the complete list of changes:
https://github.com/2fdevs/videogular/blob/master/CHANGELOG.md
{'source': 'GithubIssues', 'repo_name_with_owner': 'videogular/videogular', 'issue_id': 59860303, 'repo_stars': 1488.0}