More accurate title: "my personal use-case for grunt/gulp will no longer be necessary once HTTP2 is widely available."<p>As for my team, we use SASS to add enhanced featuresets to CSS (like variables, functions, and mixins), Typescript to add compile-time typechecking to our rather-large SPA codebase, and yes, we do concatenate+minify our transpiled Typescript.<p>We use grunt to, in order:<p>1. Package our Angular templates as a prebuilt module that populate's Angular's template cache, so we don't have to fetch them over the network at runtime <i>and</i> we're one step less susceptible to browser caching issues.<p>2. Compile our SASS to CSS<p>3. Compile our Typescript to Javascript<p>4. Concatenate and minify the resulting Javascript<p>5. Run unit tests<p>6. Add version+build numbers as query strings to our script tags (<script src="foo.js?v=1.25.11512"></script>)<p>The concatenation+minification is the last-step implementation detail. But just having server push (which, by the way, your very short blurb doesn't explain or even mention) gives us only one arguably-smaller piece of our usecase for grunt.<p>So yeah, not dead. Not even close.