chore: Support Node LTS and other ranges

[maschad]

The current Node LTS is v20.12.2 with v22 currently available

We currently only support two node versions i.e. ^18.18.2 || ^20.0.0

we should at the very least support the LTS and look to support a range of older and newer versions i.e. 18.18.x -> 22.0.x for example

[arboleya]

We already support a range, but yes, let's add ^22 to the mix.

In this case, I don't know if we still need to support ^18.

[maschad]

We already support a range, but yes, let's add ^22 to the mix.

In this case, I don't know if we still need to support ^18.

My apologies I should've been clearer, but our current package.json only supports either ^18.18.2 || ^20.0.0 , if we try testing on node v19.7.0 for instance (which is in-between 18 & 20) we will get an error.

As opposed to having a broader range support for node engines

such as

{
    "engines": {
        "node": ">=18",
        "pnpm": ">=8"
    }
}

I think it's still worthwhile to support node 18 but I have no data on consumers' environments.

[arboleya]

IIUC, versions 19 and 21 never reached glory and are about to die.

• https://github.com/nodejs/release

Also, we can't use something like >= 18 because we can't guarantee that new majors won't break the SDK.

This is why using ^N is preferred as it allows for patches and minors, but not majors.

[maschad]

All good points.

let's add ^22 to the mix.

agree with your original suggestion then