ECMAScript 2015 (ES6) was officially finalized this week. After six years since ES5, JavaScript has classes, modules, arrow functions, promises, and dozens of other features. This should feel momentous, but the reality is most developers have been using these features for months via Babel.
The standard finalizing doesn't change what we write—it changes the legitimacy of writing it.
The ES6 transpiler landscape has a clear leader: Babel. Renamed from 6to5 just last month, Babel is rapidly becoming the standard way to write modern JavaScript today. After a year of Traceur vs 6to5 debates, the community is consolidating.
Twelve months ago, the JavaScript landscape looked different. Angular dominated frontend. Grunt was the build tool. ES5 was the language. Bower handled frontend packages. Node was interesting but niche.
Today, everything's in flux. React is challenging Angular. Gulp is challenging Grunt. ES6 is being used via transpilers. npm is taking over from Bower. Node powers build tools everywhere.
Let's look at what changed and what it means.
The next version of JavaScript—ES6, or ECMAScript 2015 as it'll officially be called—is taking shape. Finalization is expected next year, but transpilers like Traceur let us use features today. The question is: which features are stable enough to bet on, and which might change?