Pin node and npm versions

[jbojcic1]

This is to make sure all devs are using the same node and npm versions. Strict setting will make the npm command with an incorrect version fail with the appropriate message

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
boardwalk	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 30, 2024 10:18am

[jbojcic1]

Seems like vercel is trying to use version 18. We should update vercel too to make sure the same version is used locally and on hosted envs

[jbojcic1]

Also seems like the max node version supported by aws lambda (and thus vercel) is 20 so we will need to decrease our local versions too.
@gudnuf are you ok with decreasing it locally to v20 (I suggest using nvm to manage node versions locally)?

[jbojcic1]

Actually seems like vercel only supports pinning major version https://vercel.com/docs/functions/runtimes/node-js/node-js-versions#version-overrides-in-package.json. I got the warning on this build:

I don't like that we can't control the exact version but I'll guess we will have to work with it. I'll then update the pr to only specify the major version too

[jbojcic1]

this now means that vercel will always build with latest node version 20 and locally you will be forced to use any version 20. however if you use nvm it will still use 20.18.0 as specified in nvmrc. that way at least dev locally can be in sync

[gudnuf]

are you ok with decreasing it locally to v20

yea this is fine

[gudnuf]

looks good, thanks!