package.json has no engines field, so there's nothing stopping (or even warning) a contributor from running this on an incompatible Node version — relevant for a project onboarding many external GrantFox contributors who will each have their own local Node setup.
Scope: Add an engines.node field matching whatever version this project is actually built/tested against (check .github/workflows/ and any Docker/CI config for the Node version already in use elsewhere, so this doesn't introduce a new, undocumented requirement — it should just make an existing implicit one explicit).
Acceptance criteria:
engines.node is set to match the version already used in CI
npm install on that Node version proceeds without a new warning
package.json has no engines field, so there's nothing stopping (or even warning) a contributor from running this on an incompatible Node version — relevant for a project onboarding many external GrantFox contributors who will each have their own local Node setup.
Scope: Add an engines.node field matching whatever version this project is actually built/tested against (check .github/workflows/ and any Docker/CI config for the Node version already in use elsewhere, so this doesn't introduce a new, undocumented requirement — it should just make an existing implicit one explicit).
Acceptance criteria:
engines.node is set to match the version already used in CI
npm install on that Node version proceeds without a new warning