2 ms·
> But most of the time this is in the context of Node.js development, and in every case I use Babel.js to turn the end result into ES5 code. If it's helpful: t
by nailer 11y ago
> But most of the time this is in the context of Node.js development, and in every case I use Babel.js to turn the end result into ES5 code.
If it's helpful: the current stable node (4.x) already supports ES6 out of the box.
- mercer 11y agoI'm currently doing that for a project, but I'm about to change things up and use Babel anyways, for the following reasons: - my project contains jsx files, which currently are compiled into .js files which feels a bit messy. - I'm seriously considering using ES7's async/await functionality, which is not supported by node yet. - and most importantly: node's ES6 support is incomplete. In particular, I miss default function parameters and destructuring assigment. Using Babel would solve all these issues, and I could simply remove Babel once support is sufficient.