Use wrtc as a `peerDependency

[piranna]

Fix #7

[piranna]

Can this be reviewed and merged?

[t-mullen]

wrtc is an interface, one implementation of which is node-webrtc (the module available on NPM). There are others - including https://github.com/mappum/electron-webrtc. Changing this to a peer-dependency prevents devs from choosing an implementation.

Thanks for your interest in this project - please keep in mind it is a WIP and barely functions.

[piranna]

wrtc is an interface, one implementation of which is node-webrtc (the module available on NPM). There are others - including mappum/electron-webrtc.

Not like this... wrtc is a npm module, that node-webrtc is it's repo name. The interface is the W3C WebRTC API.

Changing this to a peer-dependency prevents devs from choosing an implementation.

Not really, since the project makes use of wrtc non-standard APIs. Once we get rid of them and use just only the W3C APIs, then it would make sense to allow to pass the actual implementation object as parameter, but then maybe we would need to change the project name to reflect that too.

Thanks for your interest in this project - please keep in mind it is a WIP and barely functions.

That's why I have proposed these changes, we are currently using them in production code :-)