For anyone using TypeScript to build your Node.js code, you can now switch your target to es6/es2015 in your tsconfig.json:<p><pre><code> {
"compilerOptions": {
"target": "es2015",
"module": "commonjs"
}
}
</code></pre>
Assuming you're not using that 7% (<a href="http://node.green/" rel="nofollow">http://node.green/</a>) :)<p>Just make sure to update your package.json to take a hard dependency on Node 6+ if you do that:<p><pre><code> { "engines" : { "node" : ">=6.0.0" } }
</code></pre>
This will make it so that ES6-compat is assumed and TS won't transpile ES6 functionality, but it will use commonjs for modules, which means your TS will almost be a 1:1 mapping with the compiled JS and everything should just work.
FYI for anyone looking for the downloads, v6.0 technically hasn't been released yet. It will most likely be out within a few hours.<p>Edit: of course right after I say it isn't released, it is released. :)<p>Release post: <a href="https://nodejs.org/en/blog/release/v6.0.0/" rel="nofollow">https://nodejs.org/en/blog/release/v6.0.0/</a>
On a related note, does anyone know if there's a way to tell Babel that your compilation target is Node.js v6.0 and only have it compile stuff that isn't natively supported yet?<p>Edit: Thanks for all the answers. I just went through the list of unsupported features and as I'm not using any of the remaining 7%, I might be able to get rid of Babel during development if I'm lucky.<p>Edit 2: Oops, still no es6 module support :(
I've been a front end developer for, well, quite a while, and in that time we've gone from cycles of around a decade (thank you IE6!) for new versions of JS to something closer to a couple of years.<p>The future, as I see it, is incredibly bright.
And now available on Google App Engine (Flexible Environment).<p>Example app running v6.0.0: <a href="http://nodejs600.appspot.com/" rel="nofollow">http://nodejs600.appspot.com/</a>
For those curious about the performance improvements, <a href="https://benchmarking.nodejs.org" rel="nofollow">https://benchmarking.nodejs.org</a> has you covered.
I'm using webstorm to write a node app. I'm using ES6 and webstorm transpiles it to 5.1. Details here:<p><a href="http://blog.jetbrains.com/webstorm/2015/05/ecmascript-6-in-webstorm-transpiling/" rel="nofollow">http://blog.jetbrains.com/webstorm/2015/05/ecmascript-6-in-w...</a><p>I'm using node 5.9.1 and webstorm creates a <i>-compiled.js and </i>-compiled.js.map file for each transpiled file.<p>If I use Node 6 which I understand is now up to 95% support for ES6, do I still need to transpile to ES5.1? Is anyone else using webstorm with ES6 and are you also going through this transpiling step?
"Fastest Growing Platform"<p>Does this refer to growth in number of users or in number of modules? Or maybe just counting the number of lines of code?
This is a great news.<p>Are there any tools that statically or otherwise checks any potentially breaking pieces in the Node v4+ codebase/dependencies?
Note that the require mechanism is quite flakey, and they are discussing a new release or even reverting
<a href="https://github.com/nodejs/node/issues/3402#issuecomment-215166795" rel="nofollow">https://github.com/nodejs/node/issues/3402#issuecomment-2151...</a>
babel sucks - I never though I could hate something so strongly.<p>Just today I had to deal with the fact that babel wraps ALL your generators in some shit function.<p>Why ? just why ? generation function was supported in browsers longer then the age all the babel maintainers combined.<p>The worst part is I do not use babel myself - I wouldn't touch it with a ten foot pole but am forced to use it due to my stupid cowokers writing everything using babel - ( why does babel need .babelrc file ?? - is babel such a prominent part of your life that you need .rc files ?? and why does the .rc file need to be specified in every freaking folder ! )<p>1) babel's docs are also terrible<p>2) The people maintaining babel seem to actively market babel and then at the same time ignore questions and requests for better docs from the community.<p>3) Slowest compiler I have had the pleasure of dealing with - my babel watch process consumes a grand total of 150 MB of memory !!<p>Edit - had to follow HN guidelines