Re:The cost of transpiling ES2015 in 2016
by alessioalex on Monday February 08, 2016 @11:01AM
(#11058798)
I'm just wondering why not use npm scripts instead of Makefiles? They work in Windows as well and they're easier to understand (at least imo).
[ Parent
| on HN ]
Re:The cost of transpiling ES2015 in 2016
by Arnavion on Monday February 08, 2016 @01:32PM
(#11059943)
As long as they're single commands. Running multiple commands using `&&`, etc. is unfortunately not portable.
Re:The cost of transpiling ES2015 in 2016
by jdmichal on Monday February 08, 2016 @02:30PM
(#11060335)
What platform does `&&` not work on? It works fine in Windows `cmd`, which is the typical shell to worry about portability with.
Re:The cost of transpiling ES2015 in 2016
by Arnavion on Monday February 08, 2016 @04:36PM
(#11061056)
cmd's `&&` is the equivalent of bash's `;`. bash's `&&` has no equivalent in cmd.
Edit: Never mind, I'm apparently wrong.
Re:The cost of transpiling ES2015 in 2016
by jdmichal on Monday February 08, 2016 @04:45PM
(#11061105)
On Windows 7; note the lack of version information from Java:
> rm test.txt && java -version
rm: cannot unlink entry "test.txt": The system cannot find the file specified.
Re:The cost of transpiling ES2015 in 2016
by joshuacc on Monday February 08, 2016 @04:30PM
(#11061023)
That's not correct. I use npm scripts with `&&` on Windows many times per day. Other features may not be portable, but that one definitely is.
Re:The cost of transpiling ES2015 in 2016
by ThePhysicist on Monday February 08, 2016 @12:56PM
(#11059668)
I haven't looked at those yet, sounds interesting though!