The real intention of a makefile is to specify dependencies, and how to (re)build targets if they are out of date compared to their dependencies. That is traditionally used to build e.g. C or C++ projects, and can indeed quickly become very cumbersome. Almost nobody writes them by hand for larger projects. These days almost everybody uses either some makefile generator or a more modern alternative to make.
Early in my re-entry to web I was using grunt to manage the build processes, but that fell away fast—
I'll either write a Makefile or a shell script to manage those builds and processes now—and I'm far more productive for it. No need for a number of plugins and yet more dependencies to manage.
Though, I have to say I've seen less and less of Grunt and Gulp (etc) in modern JavaScript (especially TypeScript)
What you mention is the main reason for that claim.
The main less I take from this is that a) it still pays to keep it simple and b) as an industry we should continue focusing on reducing maintenance costs as much as we chase after the cool new project of the week.