[–] banhfun 9y ago ↗ If you're adopting ES6 into your stack, you may as well go all the way and support ES2017 features. [–] wildpeaks 9y ago ↗ If you stick to ES2015 features that Node 6/7 support, you can skip transpilation node-side though. Depending on the project, that can be quite convenient. [–] akmittal 9y ago ↗ I always felt transpiling on server side as unnecessary overheard, Node 6/7 support most of new features it's too much to transpile for 1-2 features. [–] agnivade 9y ago ↗ Any good reference for ES2017 ? I believe the documentation is still lacking. [–] akmittal 9y ago ↗ Exploring ES6 author is wrting es2016-17 book also http://exploringjs.com/es2016-es2017/index.html#toc_ch_objec...
[–] wildpeaks 9y ago ↗ If you stick to ES2015 features that Node 6/7 support, you can skip transpilation node-side though. Depending on the project, that can be quite convenient. [–] akmittal 9y ago ↗ I always felt transpiling on server side as unnecessary overheard, Node 6/7 support most of new features it's too much to transpile for 1-2 features.
[–] akmittal 9y ago ↗ I always felt transpiling on server side as unnecessary overheard, Node 6/7 support most of new features it's too much to transpile for 1-2 features.
[–] agnivade 9y ago ↗ Any good reference for ES2017 ? I believe the documentation is still lacking. [–] akmittal 9y ago ↗ Exploring ES6 author is wrting es2016-17 book also http://exploringjs.com/es2016-es2017/index.html#toc_ch_objec...
[–] akmittal 9y ago ↗ Exploring ES6 author is wrting es2016-17 book also http://exploringjs.com/es2016-es2017/index.html#toc_ch_objec...
6 comments
[ 2.9 ms ] story [ 27.5 ms ] thread