Change Node 16 moduleResolution to "Node16"

[luis815]

Issue

Current moduleResolution value is "node". This doesn't seem to support "exports" in package.json.

Possible Solution

Change moduleResolution to "Node16" seems appropriate. A quick test overriding the value after extending this configuration seems to solve the issue.

[orta]

It is a good question of when people might expect esm projects to be the default, but I'm not quite sure that is right now.

I'm open to having a separate node16+esm (we already have a node16+strictest+esm for example) but I don't think changing the default is a good call for maybe a few years

[voxpelli]

+1 on a node16+esm if the main one can't have it

[orta]

Sure thing, add it

[Gerrit0]

when people might expect esm projects to be the default

If module is set to commonjs, moduleResolution can be set to node16 to allow import/export maps to work properly while still emitting cjs

[Gerrit0]

Actually, that seems to not even be required.

https://www.typescriptlang.org/tsconfig#module

I'm using node16 in the beta branch for TypeDoc and am getting cjs output as expected.

[bradennapier]

In typescript 5.2 it is an error to have moduleResolution set to node so we will need a separate esm vs cjs option.

Currently with 5.2 the node18 base config does not work. It requires you add Node16 as moduleResolution which will force esm support which makes it impossible to use with our project.

Looks like module will need to change

https://devblogs.microsoft.com/typescript/announcing-typescript-5-2-beta/#module-and-moduleresolution-must-match-under-recent-node-js-settings

microsoft/TypeScript#54620

[orta]

This happened in #197