Do we want to allow for users to stage-x plugins with this preset as well?
Or should this only cover for everything under latest?
Since browsers don't implement stage-x features anyway (otherwise they'd be stage-4), it would be only supported by browsers through a flag...
Maybe we should just leave it alone and users will just specify stage-x presets individually?
Actually now that I think about that seems fine?
My vote is for not supporting stage-x features.
If there's a case, or could be in the future a case, where a vendor has implemented stage-x features without any special flags needed, then the project should definitely take advantage of that.
However, I'm not that familiar with the stage system - is that a likely or even possible scenario?
Agreed, Yeah after I brought it up it doesn't really make sense to do except under a flag/canary release for a browser and that would only be at minimum stage 3 by definition anyway.
We would only do this if you were using that for development and wanted the clearer output etc instead if source maps or something - not really a priority unless someone wants to take this on.
Ok yeah it makes sense to just support all plugins in latest (http://babeljs.io/docs/plugins/preset-latest/) - currently up to es2017.