🐛 BUG: Requiring Node ^14.20.0 breaks on CodeSandbox

[delucis]

What version of astro are you using?

v1.0.0-beta.72

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

n/a

What package manager are you using?

yarn

What operating system are you using?

CodeSandbox (Linux container?)

Describe the Bug

Astro’s engines field in package.json requires Node to be ^14.20.0 || >=16.14.0 but CodeSandbox is currently running on 14.18.1 so trying to use one of the example projects from astro.new results in an error:

error [email protected]: The engine "node" is incompatible with this module.
Expected version "^14.20.0 || >=16.14.0". Got "14.18.1"

Same applies if we were to configure our CodeSandbox templates to run Node 16. They currently ship 16.12.0 which also falls outside of our semver range. (Thanks @hippotastic for checking that!)

Are we safe to roll back even further in engines? There are several security patches between 14.18.1 and 14.20.0 (see CHANGELOG), but in this case we’re allowing people to choose to use those, not forcing them to. Paging @ran-dall as he worked on the last rollback.

Interesting side note: CodeSandbox evidently persist their project containers so if you follow a link from astro.new, those projects error with the above message but then successfully start running using beta.65 — presumably because it was previously installed. Once you fork the sandbox there is no existing installation so the whole thing fails.

Link to Minimal Reproducible Example

https://codesandbox.io/s/astro-engines-repro-fjbkvp

Participation

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