Use tinyexec

[bluwy]

Changes

This switches to use tinyexec instead of execa for the places where we execute scripts:

1. astro add
2. astro docs
3. pnpm benchmark (our internal benchmark scripts)
4. smoke tests

Our test-utils still use execa as I find it harder to migrate. We use some execa specific features to read the output. I don't think it's a big deal for now so left it as is. The rest are easier to migrate as we only execute things and not read its output much.

Testing

I tested the first 3 manually locally, which works (including if I try to ctrl-c the process, or cut off the internet connection and regain connection again). The smoke tests should be covered and passing in CI.

Docs

Added a changeset in case this breaks something

[changeset-bot]

🦋 Changeset detected

Latest commit: a85eedb

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Fryuni]

What is the advantage of tinyexec over execa?

From the code changes I expect that it would fix problems in case astroBin is a path containing spaces, but is there some other reason for the change?

[bluwy]

The main reason (which I forgot to mention) is that it's much lighter and does what we only need. With execa, it provides a lot of features by default but that also brings in a lot of dependencies, which most we don't really utilise.

So with this PR, we switch to a smaller library to only execute commands (which is a nicer wrapper API over child_process that's awkward to use in practice). That way users don't have to pay for installing more dependencies that aren't really used in practice. You can check execa's dependencies at https://npmgraph.js.org/?q=execa%408 (we're using v8, but v9 is much larger if we upgrade)