I really don't. It puts one tool in the position of having to be good at all those things; and implicitly puts one ecosystem in a privileged position compared to everything else in the project by default, rather than by choice. It also means the file format of that one tool needs to be hammered into shape for every use case, and if it's something lobotomised like JSON, everyone suffers.

Give me a Makefile any day. Yes, that's a specific choice of top-level tool, but it's a better choice than most for that specific top-level job because you just shell out to whatever else you need. Not having to rebuild dependency management is a win, too, where you can take advantage of it.