🐛 BUG: Rollback Nodejs Dependancy

[ran-dall]

What version of astro are you using?

[email protected]

Are you using an SSR adapter? If so, which one?

N/A

What package manager are you using?

npm

What operating system are you using?

Linux

Describe the Bug

I've been manning support threads today, and during troubleshooting, I found out that [email protected] depends on node: '^14.20.0 || >=16.16.0, however the issue with that there are many distros that haven't stabilized 16.16.0, including Red Hat, Microsoft (both CBL Marinier and VSCode's Devcontainer images), Debian (which is probably the most important one), and Gentoo (had to give Gentoo a plug).

I've been advised by both Red Hat and MS's VSCode teams that the best solution would be to downgrade our Nodejs dependency to 16.15.1 (or even 16.14.0, as it's the most consistent and stable across distros).

Debian Ref: https://packages.debian.org/sid/nodejs
Gentoo Ref: https://packages.gentoo.org/packages/net-libs/nodejs
Red Hat Ref: https://access.redhat.com/downloads/content/nodejs/16.14.0-4.module+el8.6.0+15294+54b291d2/x86_64/fd431d51/package (it may require employee or customer access, so I attached a screenshot)

FWIW: Arch DOES have 16.16.0 in the gallium branch, and Homebrew does have 16.16.0 as node@16, but it seems no one else does.

ping @matthewp @aFuzzyBear

Link to Minimal Reproducible Example

N/A

Participation

• I am willing to submit a pull request for this issue.

[ran-dall]

FWIW This break VSCode Devcontainers and GitHub CodeSpaces, as both use dpkg packages on their official images (both share images, I'm almost sure).

[matthewp]

This was changed in #3871

Not sure what to do here, @natemoo-re has more context on why this was changed. If we have to choose between an astro add bug or not having Astro work in CodeSpaces, etc. I think we probably have to accept the astro add bug, but maybe there's another way.

[ran-dall]

@matthewp To be clear, though, this makes Astro break on (most) all Linux-based modes of operation. I can't even run it on my Gentoo (which is supposed to be pretty progressive), as Gentoo doesn't even have 16.16.0 uploaded for testing. (I'll make an ebuild today for it, though)

To give you an idea of the significance of that, Gentoo (distro differ) has a 30-90 day stabilization period before stabilizing a new package version. This is worth considering since most distros don't even have 16.16.0 in for testing (not just Gentoo, but Debian is a big one, for instance), so it might be a few months+ until we see 16.16.0 stabilized across Linux.

[ran-dall]

I made a PR in Gentoo for Node 16.16.0 (gentoo/gentoo#26384). I already have PR open with Red Hat for rpm. I'm going to try to get in touch with someone who has authority in the deb ecosystem and see if I can push that along too.