rauschma
commented
7 years ago - We need better support for the majority’s choice, “Let me see the results!”. ;-)
- Nice property of requiring untranspiled code to be compatible with preset-env (=stage 4 or older): old code remains compatible/usable forever.
- Unclear: how is updating source code (e.g. whenever preset-env supports a new feature) best handled? Concern: may break existing code that depends on a given package.
Didn't talk about this (brought it up the last last meeting in the roadmap), I do want to mention @rauschma https://twitter.com/rauschma/status/870730837620404224 again - not really something Babel does but thinking about our recommendation/thoughts on publishing non-ES5 (and beyond) and how we should do it as an ecosystem since it gets brought up a lot and only more so as browsers/node supports ES6.