Propose moving to node v20.12.2 in docs due to errors when testing

[nathanwilk7]

What's being changed:

Propose moving to suggesting node v20.12.2 because of a package error when running on v19.9.0 just now (on an arm64 macbook).

Also removes node from nvm install node 19.9.0 because nvm was ignoring the version when I ran this.

Type of change:

• README

How Has This Been Tested?

• Github action – automated build completed without errors
• Local build - the site works as expected when running yarn start

Ran yarn build locally

[nathanwilk7]

Are there other places in this repo like CI/CD/testing the default node version should be bumped from 19 to 20? Also left some comments in the PR

[nathanwilk7]

Previous behavior

nvm install node 19.9.0
v22.0.0 is already installed.

New behavior:

nvm install 20.12.2     
v20.12.2 is already installed.

note

nvm --version
0.39.5

[nathanwilk7]

Using node v19.9.0, got:

nvm use 19.9.0
yarn install

yarn install v1.22.22
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
warning Resolution field "eta@1.13.0" is incompatible with requested version "eta@^2.0.0"
warning Resolution field "eta@1.13.0" is incompatible with requested version "eta@^2.0.0"
warning Resolution field "eta@1.13.0" is incompatible with requested version "eta@^2.0.0"
[3/5] 🚚  Fetching packages...
error nanoid@5.0.7: The engine "node" is incompatible with this module. Expected version "^18 || >=20". Got "19.9.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

[daveatweaviate]

@databyjp I think @nathanwilk7 is running into the same thing I did when I set up locally. Our tool chain is aging and we're starting to hit compatibility problems. Let's talk to @sebawita about updating. I think you two have a better idea about what's involved.