News for hackers. Stuff that matters.
Re:The cost of transpiling ES2015 in 2016 by faizshah on Monday February 08, 2016 @12:16PM (#11059370)
After wrestling with creating a nice gulpfile for the past two days (essentially wasting two days), I think this is the right route. My biggest gripe with gulp is that creating reusable pipelines even with lazypipe is unnecessarily difficult and can make debugging build scripts (!) hard.

Can you post an example of one of your makefiles?

Re:The cost of transpiling ES2015 in 2016 by ThePhysicist on Monday February 08, 2016 @12:56PM (#11059656)
Sure!

https://github.com/adewes/gitboard/blob/master/Makefile

This one is rather simple but includes steps for building and optimizing JS and CSS. It also has support for different build environments (Gitboard has a Chrome version and a web version).

Re:The cost of transpiling ES2015 in 2016 by rafael-rinaldi on Tuesday February 09, 2016 @01:27AM (#11063517)
I used to go with Makefiles maybe two years ago but there's really no point on using anything else other than npm scripts if you already have a Node.js set of tools (therefore an npm manifest).

One great thing about npm scripts is that every time you run a command Node.js will export the binaries path to your $PATH so you don't have to manually add absolute paths.