- Using ES6 right now
- Get TypeScript
We’re nearing the 7.0 Babel release. Here’s all the cool stuff we’ve been doing.
Please join and help us! My story Those are some of the reasons I get excited to work on this project each day, especially as a maintainer. As for me, I recognized a need and an interesting project. How do we grow our community in terms of the number of maintainers versus of the number of users?
We’re nearing the Babel release. Here’s all the cool stuff we’ve been doing.
This could simply mean thinking about the mental and emotional burden of maintainer-ship. A developer could wait until all the browsers they care about support ES6, but that would take forever. Instead our best hope is to compile ES6 down to ES5 via a method called transpiling.
You could start using ES6 simply by using only one of its features, like arrow functions. The table illuminates a couple of problems with supporting ES6 natively: None of the Internet Explorer browsers from 11 on down significantly support any ES6 features and never plan to either.
A developer could determine if the browser supported a specific API such as geolocation and act accordingly. A lot of what ES6 is introducing comes with new syntax. ES6 support differs greatly among JS engines, so support for a given feature does not serve as a proxy for support of some set of ES6 features you would like to use.
Moreover, you still need an ES5 version of your code to use when the feature detection fails. Transpilation tools So with all of that said, your best bet is to use a transpilation tool, which will compile your ES6 code into ES5 code, making it cross-browser really cross-engine compatible.
Transpiling is the process of compiling source code into another form of source code.