scripts/deploy.mjs and scripts/invoke.mjs use ESM ("type": "module" in package.json) and modern top-level main().catch(...) patterns that assume a reasonably current Node.js. Nothing declares what "reasonably current" means — there's no "engines": { "node": ">=X" } field in package.json. A contributor on an old Node version would hit a confusing syntax/runtime error rather than a clear version-mismatch message. Worth adding once the actual minimum supported version is known/tested.
scripts/deploy.mjsandscripts/invoke.mjsuse ESM ("type": "module"inpackage.json) and modern top-levelmain().catch(...)patterns that assume a reasonably current Node.js. Nothing declares what "reasonably current" means — there's no"engines": { "node": ">=X" }field inpackage.json. A contributor on an old Node version would hit a confusing syntax/runtime error rather than a clear version-mismatch message. Worth adding once the actual minimum supported version is known/tested.