chore: Add node-version to package.json and workflows

[baruchiro]

Added .node-version file and updated GitHub Actions workflows to use it for Node.js version management.

[cliffhall]

Hi @baruchiro!

This seems nice, but I'd much rather use package.json for the file as opposed to adding yet another file to the root of the project for a single variable.

Docs for setup-node show how you can do this. (note, using setup-node@v5):

In main.yml

      - uses: actions/setup-node@v5
        with:
          node-version-file: package.json
          cache: npm

and in package.json

{
  "engines": {
    "node": ">=22.0.0"
  }
}

[cliffhall]

@baruchiro Any interest in updating the PR to use package.json as the source of the version? I still think this is a good idea.

[baruchiro]

@cliffhall updated.

However, I have noticed the Dockerfile versions are 24 and not 22 as declared in README: ^22.7.5.

[cliffhall]

However, I have noticed the Dockerfile versions are 24 and not 22 as declared in README: ^22.7.5.

@baruchiro Could you update the version to (>=22.7.5) in package.json and README?

For reference, that value was set by this PR where the contributor said that an error was reported for versions less than 22.7.5.

The problem was related to the Fetch API, and what I found was:

The lowest Node.js version where Fetch is natively supported and stable on both Windows and macOS is Node.js 21. While Fetch was introduced as an experimental feature in Node.js v18, it became fully stable and supported in Node.js v21. Prior versions like v12.20.0, while supporting node-fetch (a library that implements Fetch), don't offer the built-in Fetch API.

But to be safe, I'd keep it at 22.7.5 or higher.

[baruchiro]

@baruchiro Could you update the version to (>=22.7.5) in package.json and README?

Only needed in the package.json, done

[cliffhall]

LGTM! 👍

[cliffhall]

Resolved properly