Had some experience with it in BigCorp™. I don't love it, but it works. It's just a plugin that will install node (and npm), run `npm instal` and then run the s

Had some experience with it in BigCorp™. I don't love it, but it works. It's just a plugin that will install node (and npm), run `npm instal` and then run the specified gulp task. The good part is that it's not that bad to fit within the company infrastructure, particularly if it's a BigCorp kind of thing. It's interesting because it allows you to play well with CI processes and quality rules - I'm thinking about tests here. With this kind of setup, you can make the front-end build fail if e.g. code coverage drops below a given threshold, using the same setup you use for other components. The boring part is that it's yet another place to put config info. A particularly ugly one which reeks of over-engineering IMHO. Also it's XML; XML isn't quite the song of the front-end people, at least config-wise. :)