ES6 all the things! #125
Description
Seeings as how easy it was authoring in ES6 and using BabelJS to publish in feathers-commons I would suggest to migrate the main repository over to that workflow as well and also pull feathers-commons back in.
With #124 the shared functionality that I initially intended feathers-commons for is all contained in here again so there is no point in pulling it out in 1.x versions. It will make sense for version 2 since I would like to put the providers into separate modules like feathers-rest, feathers-socketio, feathers-primus etc.
Also:
