Drop Node 14 support

[Rich-Harris]

Describe the problem

Now that even AWS lambda have finally got their act together and shipped Node 16 support (just in time for Node 18 to be the current LTS version), I'm not sure there's much of a reason to continue supporting Node 14?

Dropping it would simplify the test matrix slightly, and would allow us to get rid of this grotesque crypto stuff:

kit/packages/kit/src/runtime/server/page/csp.js

Lines 23 to 33 in 7609ad0

	// TODO: remove this in favor of web crypto API once we no longer support Node 14
	const name = 'crypto'; // store in a variable to fool esbuild when adapters bundle kit
	csp_ready = import(name).then((crypto) => {
	generate_nonce = () => {
	return crypto.randomBytes(16).toString('base64');
	};
	generate_hash = (input) => {
	return crypto.createHash('sha256').update(input, 'utf-8').digest().toString('base64');
	};
	});

If Lambda supporting 16 isn't a good enough reason, then presumably we have to continue supporting 14 until it's out of LTS on April 30 next year. That doesn't seem ideal.

Describe the proposed solution

Only support Node 16 and above

Alternatives considered

No response

Importance

would make my life easier

Additional Information

No response

[Mlocik97]

I would say it's little early... but not that much it would be big problem...

For example my systems will update to Node 16 or 18 together with system update (to Ubuntu 22.04.1 LTS at 4th august this year). Even tho, yes, Node 16 and even 18 is available for Ubuntu 20.04.4 LTS.

[ghostdevv]

I don't use Node 14 myself but it would be good to keep in mind there might be some teams still using it, we still got just under a year of Node 14 being supported by Node:

[Rich-Harris]

We debated it among the maintainers and support for dropping 14 was universal, since if Lambda supporting 16 isn't a solid enough reason then there'd be no point at which we can drop it prior to April 2023.

All the relevant deployment platforms support 16, and it's very easy for people to switch locally with tools like nvm, so the only reason we can see for someone being unable to use 16 is that they have some dependency that only works with 14 (which candidly I'm unsympathetic to — 16 has been out for over a year and has been the active LTS version for well over 6 months)