Re:Hard-won lessons: Five years with Node.js
by chrisco255 on Thursday April 20, 2017 @03:38AM
(#14154693)
Totally false. Node.js pre-dates Babel by about 6 years so I wonder how that could possibly be true. Second, most ES6 features are already included natively in latest versions of Node so no need to transpile at all. You can even get async/await out of the box.
[ Parent
| on HN ]
Re:Hard-won lessons: Five years with Node.js
by sgift on Thursday April 20, 2017 @04:12AM
(#14154820)
No one cares how you wrote 6 years ago, today the way to do it (as I've been told by many people who write NodeJS applications all the time) is to use transpilers. And:
> most ES6 features
Most. Ugly word. Really ugly word.
Re:Hard-won lessons: Five years with Node.js
by throwanem on Thursday April 20, 2017 @05:19AM
(#14155144)
That's a way to do it. It is not the only way to do it, even if some people do it that way all the time.
I might add a transpiler for Typescript to my stack soon, if that language turns out as pleasant to work with as I've been hearing. If I do, it'll be the first time I use one. And I've been working with Node, in production, since 2013.
Re:Hard-won lessons: Five years with Node.js
by sgift on Thursday April 20, 2017 @06:07AM
(#14155365)
Go away. I've invested weeks to learn something which at least resembles NodeJS best practices and now you come along and say "nope, we do it different" ... :(
(That was a joke btw. Thanks for the info. The consensus seemed to be that Babel is the way to go, but if your variant works for you good to hear. I will still stay with it. I like ES6 imports in Node.)