> npm is require to run many command line tools (grunt, gulp ...etc) You seem to be looking for the ability to run JS tooling (builders, transpilers, minifiers

> npm is require to run many command line tools (grunt, gulp ...etc) You seem to be looking for the ability to run JS tooling (builders, transpilers, minifiers) as common command line utilities. That seems to be entirely possible and I'm not sure why you're making the distinction. I can pipe input between all of them, include them in bash scripts, make files, whatever else you're used to. There's no meaningful distinction between a "standalone command line tool" and a command line tool that is written in node. If I added webpack (for example) to an ubuntu package repository, you could do `apt-get install webpack`, and have a "standalone" command line utility without ever downloading it from npm. It would have to pull other ubuntu packages as dependencies, but that's standard practice for installing something these days. Unless you're wondering about packaging it into linux. In which case I'm just as confused as you are.