Downgrade cli-boxes

[fregante]

Fixes #97 (comment)

In short, the upgrade caused issues because the boxen has supported "node 18" and not every one of those users are on "node 18.20" yet.

See reports in:

• Build broken in Astro 4.11.6 withastro/astro#11480

Since there are no improvements in v4, it's easier to stay on v3 for now.

[fregante]

Technically [email protected] has always been ">=18.20, >=20.10". Should I just bump the engines instead? See:

• Explicitly define Node 18.20+ support #103

---

https://nodejs.org/api/esm.html#import-attributes

[fregante]

update-notifier included v8.0.0 in a minor release, probably breaking a few systems:

yeoman/update-notifier@ad04288

This sequence would fix the situation:

1. merge this
2. release v8.0.1
3. merge Explicitly define Node 18.20+ support #103
4. release v9.0.0

[Caesarovich]

LGTM !

Dealing with engine versions is always a big pain. We'll have to be more careful next time.

Could you trigger a release @sindresorhus ? Thanks

[Caesarovich]

Also I propose that we finish the ongoing enhancement PRs (such as #99) before publishing v9. That way it wouldn't be too much for nothing.

[fregante]

We'll have to be more careful next time

It's kinda difficult because the CI is set to "node 18" but it points to "the latest node 18". Even if you manually check, the engines downstream isn't guaranteed to be accurate. Node >=18.20 means "node 20 is fine", but it wasn't the case here either.

• Fix engines.node cli-boxes#15