Make angular and moment as peerDependencies

[Sauloxd]

Motivation

Problem 1:
When my webpack bundles this package, it requires another whole angularjs as the md-picker

This could be resolved if I just add angularjs as an external by webpack so it bypass this (and all) angularjs require. But other libs take this approach and I also think it's better.

Problem 2:
Another issue is the #40 .
It is already using moment from the global window, so it is already a peerDependency.
Updated to latest, and no problems were seen in the built demo

Problem 3:
Make demo reference node_modules instead of deprecated bower_components. Needed to install angular-{aria,animate,message} as devDependencies

[dpoetzsch]

Your idea seems logical to me. From what I understand, a peer dependency is actually what we want.

However, shouldn't angular-material be a peer dependency as well? And what about angular-{aria,animate,message}?

Also, to make this repo work in development mode, I think one has to add angular and moment to devDependencies as well, no? In this case, the versions should be the ones from the peer dependencies. The same should be true for angular-{aria,animate,message}, no? At the moment I have angular 1.6 installed in dev environment, but angular-{aria,animate,message} in version 1.7.x, I feel this cannot be good.

[BaldemarJanrain]

@dpoetzsch If you look at the repo you forked from, you'll see that package.json does not contain any angular nor moment dependencies, only gulp-* related. In the bower.json is where you want to have your dependencies needed to develop. When you import the component you'll get a WARNING: Tried to load AngularJS more than once. message because of this dependencies being required in the package.json.