I still refer back to this excellent post from 2014:<p><a href="http:&#x2F;&#x2F;blog.keithcirkel.co.uk&#x2F;how-to-use-npm-as-a-build-tool&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blog.keithcirkel.co.uk&#x2F;how-to-use-npm-as-a-build-tool...</a><p>And the still active, linked, github repo:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;keithamus&#x2F;npm-scripts-example" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;keithamus&#x2F;npm-scripts-example</a><p>For playing with js&#x2F;css(processors)&#x2F;webpack things. I never quite understood the facination in the js community with build tools that don&#x27;t quite replace npm. It just seems like an unwelcome source of extra clocs in the toolchain.<p>I was also somewhat pleasantly surprised at the simplicity of the setup for the angular2 (beta) tutorial[a] -- even if it manages to pull down a 100mb of dev dependencies (dist dependencies are much more sane). And even if the particular tutorial stops (or did a few weeks ago) before it actually shows how to interact with <i>any</i> kind of external storage&#x2F;db&#x2F;api...<p>[a] <a href="https:&#x2F;&#x2F;angular.io&#x2F;docs&#x2F;ts&#x2F;latest&#x2F;quickstart.html" rel="nofollow">https:&#x2F;&#x2F;angular.io&#x2F;docs&#x2F;ts&#x2F;latest&#x2F;quickstart.html</a><p>[ed: actually meant quickstart+:<p><a href="https:&#x2F;&#x2F;angular.io&#x2F;docs&#x2F;ts&#x2F;latest&#x2F;tutorial&#x2F;" rel="nofollow">https:&#x2F;&#x2F;angular.io&#x2F;docs&#x2F;ts&#x2F;latest&#x2F;tutorial&#x2F;</a> ]