Specify type definitions for tsc node12 imports

[willstott101]

In tsc nightly a new module resolutions scheme is introduced called node12 or nodenext which uses this "exports" field in package.json files. When this is present and being used then the old root "types" is not used. You have to specify the types in the specific exports (when the files are not adjacent).

[lukeed]

There's no reason for this in this module. The existing layout and pkg config has all entries loading with their correct types

[willstott101]

Have you had it loading properly with typescript@next and node12 module resolution set in tsconfig? Because it failed to find types for me with that setup... unless I added these lines. I'm happy to make an MCVE if you like, or find the GitHub thread on tsc that I was reading which led me to realise this is what I needed to add.

[willstott101]

Just the clarify the node12 name may sound like it's old - but the full resolution scheme isn't even fully released in tsc yet. Support for package.json's exports field is very young in tsc it seems.

[willstott101]

microsoft/TypeScript#46452 (comment)

[chocolateboy]

Can confirm the declaration file isn't getting found for me without this on TypeScript 4.8-beta with moduleResolution set to nodenext.

(That said, I'm not sure why tsc doesn't just fall back to the top-level "types" field if all else fails, or add an option (e.g. esmcompat) to do that.)