Add multiple tsconfigs for different environments

[Ethan-Arrowood]

Adds more tsconfigs.

Why do node20 and node20-esm use the same lib and target as node18?

The lib and target fields are the same because Node.js v18 implemented support for some ES2023 methods. And since TypeScript does not allow us to specify types for individual features (and rather sets of features such as ESNext.AsyncIterable) we must use ES2023 in the lib array for Node.js v18. Furthermore, once TypeScript releases a "target": "ES2023", then the Node.js v20 configuration will be updated to that (assuming Node.js v20 fully supports ES2023).

Closes #59

[mrmckeb]

Thanks @Ethan-Arrowood! We'll need to update the root README too.

I'll ask a few people to review these and compare to what we have in our internal repos.

[mrmckeb]

Hey @Ethan-Arrowood, I've run this by a few people and the feedback is that we should focus on the lib/target versions for TypeScript and Node.js. The other settings make assumptions about the build system, which can vary greatly between projects (even our own). Instead can make use of shared monorepo configs, as you pointed out that vercel/vercel does with @vercel-internals/tsconfig.

How would you feel about updating this PR to focus on Node versions instead? As an example:

• https://github.com/tsconfig/bases/blob/main/bases/node16.json

Probably 16/18/20 would be enough for us, as we probably don't want to support anything older nor anything non-LTS.

[orca-security-us]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Secrets	0   0   0   0	View in Orca

[Ethan-Arrowood]

Alright, take a look!

[mrmckeb]

This looks great, almost ready to go.

One question - is this a breaking change? I think it might be, as there's no longer a config at @vercel/style-guide/typescript if you're using tooling that doesn't support "exports" - CC @styfle for thoughts too.

[vercel-release-bot]

🎉 This PR is included in version 5.2.0-canary.1 🎉

The release is available on:

• npm package (@canary dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[mwskwong]

@Ethan-Arrowood @mrmckeb In https://github.com/vercel/style-guide/blob/canary/typescript/tsconfig.node20.json, according to the doc: https://www.typescriptlang.org/tsconfig#lib

es2023 is not a valid value for lib and target, and TS does complain about that when using this TS config. Maybe it should be changed to esnext for now? However, I imagine we need to keep monitoring the status and change it to es2023 once it is available, since esnext will target es2024 by that time.

[vercel-release-bot]

🎉 This PR is included in version 5.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀