Remove direct RxJS dependency and have it passed to the plugin

[daffl]

That way you can use RxJS whichever way you want, it removes the hard dependency on RxJS and gets the (unminified) Browserified size down from 550k to 25k. The only thing you have to do now is pass it to the rx method when configuring:

import RxJS from 'rxjs';

app.configure(rx(RxJS, options));

@Harangue Let me know if you see an issue with this.

[jack-guy]

None whatsoever. You want to support any other libraries like Bacon in the short term? We also may want to rebrand since rx is associated with the rx-language set of libraries. Feathers-reactive, perhaps?

[daffl]

Cool. I'm not sure if the FRP library we use matters too much and if it would be worth the effort. RxJS seems pretty solid (although the new version was a little confusing at first).

I was thinking about rebranding, too. The more I think about it the more I like feathers-reactive. I was thinking of having something less FRP related like feathers-feeds or feathers-observe since people were asking about subscription and changefeeds but reactive is still the most fitting term.

[daffl]

@Harangue I renamed to feathers-reactive and published the new version that takes RxJS as a separate argument. Do you have an npm account I can add as a collaborator?