Possibly remove Babel from generated app

[daffl]

I just did some tests and I think Node 5 now pretty much supports all ES6 features that we are using in the docs and the generator except for modules (which actually isn't part of the ES6 spec anyway).

Since @marshallswain already noticed slower app startup time and higher memory consumption using Babel I am proposing to just switch the generator and all documentation examples to require imports and syntax that is supported by latest Node.

[marshallswain]

👍

[daffl]

This will also fix the demo problem submitted in feathersjs/feathers#212. As long as you are using the latest Node everything should work. In older Node versions you'll just have to use ES5 (which we will mention in the docs).

[ekryski]

k I'll convert this today.

[daffl]

We probably need to check process.version and throw an error if it is not Node 5 though. Or enable Babel in that case but I'm not sure if it's worth the effort.

[marshallswain]

Let's just provide instructions on how they can add Babel if they need another Node version.

[sscaff1]

@marshallswain @daffl Were the instructions on how we can add Babel pack ever added somewhere?

[marshallswain]

@sscaff1 I'm pretty sure they haven't been added, yet. I created this issue for it, yesterday: feathersjs-ecosystem/docs#105

[daffl]

We should definitely have a "Setting up guide" (that most importantly mentions to use nvm and also includes Babel) but the Babel setup would really just be a copy of https://babeljs.io/docs/setup (CLI or require hook). There is nothing Feathers specific that needs to be done.