> then it might be pretty fiddly for someone to clone that repo and get it running locally with node + TS, it is straightforward (and common) to generate JS ou

> then it might be pretty fiddly for someone to clone that repo and get it running locally with node + TS, it is straightforward (and common) to generate JS output at publish time for distribution. then, using the CLI tool or whatever is only a `npm install -g <pkg>` away, no extra steps. sure it's not a single binary, but I'd argue _most_ users of a general CLI utility don't necessarily care about this.