chore: update supported Node.js versions

[aduh95]

BREAKING CHANGE: remove support for Node.js 14.x

[merceyz]

It doesn't cost much, if anything, to support Node.js v14.14.0 so could you document why support for it is dropped and why specifically v16.20.0 was chosen as the minimum?

If this is approved the tsconfig should be updated to ES2021 and the esbuild target changed as well.

corepack/tsconfig.json

Line 15 in 84e6e1d

"target": "ES2020"

corepack/tsconfig.json

Line 10 in 84e6e1d

"lib": ["ES2020"],

corepack/package.json

Line 54 in 367a9fc

"build:bundle": "esbuild ./sources/_entryPoint.ts --bundle --platform=node --target=node14.14.0 --external:corepack --outfile='./dist/corepack.js' --resolve-extensions='.ts,.mjs,.js'",

[aduh95]

It doesn't cost much, if anything, to support Node.js v14.14.0

Pnpm v8 doesn't support Node.js v14.x anymore, so if we want to keep the pace, we have to drop it on CI, and if we drop it on CI, we should probably not document that we support it.

why specifically v16.20.0 was chosen as the minimum?

It's the latest v16 version, I don't have the bandwidth to test all the versions, using the latest seems easier and safer anyway.

[styfle]

I would prefer a specific version here because this is about the expectation of corepack cli being distributed with node in the current PATH.

Alternatively, we could link to the official docs that mention the versions in the first section:

Added in: v16.9.0, v14.19.0

[styfle]

It doesn't cost much, if anything, to support Node.js v14.14.0 so could you document why support for it is dropped

Another reason to drop node@14 is that it reaches EOL on 2023-04-30 in a couple weeks so newer versions of Corepack won't be distributed with future node@14 because there will be none after that date.