task VS zx

Interesting. I do something similar with my task https://github.com/kardianos/task package, which is in tern loosely based off of another package from 10-15 years ago.

Yeah, another way to do this, rather then chaining methods, is to provide a consistent interface that get called. I've seen this done a few ways, here is mine: https://github.com/kardianos/task ; don't necessarily recommend it, though I may see if generics add anything to it.

When zx first appeared, it was a tiny esm script that just proposed a new idea for how child_process.spawn API could be enhanced with string template literals.

TIL about zx! https://github.com/google/zx

This suite of tools feels indispensable. Anything to keep me from having to write/maintain bash scripts that are more than a series of commands.

Great point! According to https://github.com/oven-sh/bun/blob/b433beb016470b87850f3c01..., Bun Shell took inspiration from zx[0], dax[1] and bnx[2]

[0]: https://github.com/google/zx

[1]: https://github.com/dsherret/dax

[2]: https://github.com/wobsoriano/bnx

If you want test it, you can run this script withzx :

I really love writing with zx. https://github.com/google/zx

We have some folks who have gone wild copy-pasting random fancy bash snippets into various developer helpers scripts. Zx did like 90% of that stuff out of the box, without being a pile of chaotic custom bash.

I ended up using this for my cli scripting needs. https://github.com/google/zx