A consumer using module optionnode16/nodenext and/or or moduleResolution optionnode16/nodenext cannot access types.d.ts from the types field of any package which provides it.
Steps to reproduce
Case A
This won't be obvious unless types.d.ts exports something that the main entry point index.js doesn't. Assuming that's the case:
Create a package with module: node16 in its tsconfig.json
Import a type from a package w/ a types field where the type only exists in types.d.ts but not index.js
Observe compilation error
Case B
Otherwise, it's more subtle:
Create a package with module: node16 in its tsconfig.json
Import a type from a package with a types field
Use your editor to navigate to the reference of the type.
You will navigate to index.js.
Expected behavior
Case A: no error
Case B: should have navigated to types.d.ts
Platform environment
n/a
Additional context
This is not a problem when using the legacy node module resolution algorithm.
The solution is to add a types conditional export, as you will read in the documentation linked above.
Describe the bug
A consumer using
moduleoptionnode16/nodenextand/or ormoduleResolutionoptionnode16/nodenextcannot accesstypes.d.tsfrom thetypesfield of any package which provides it.Steps to reproduce
Case A
This won't be obvious unless
types.d.tsexports something that the main entry pointindex.jsdoesn't. Assuming that's the case:module: node16in itstsconfig.jsontypesfield where the type only exists intypes.d.tsbut notindex.jsCase B
Otherwise, it's more subtle:
module: node16in itstsconfig.jsontypesfieldindex.js.Expected behavior
Case A: no error Case B: should have navigated to
types.d.tsPlatform environment
n/a
Additional context
This is not a problem when using the legacy
nodemodule resolution algorithm.The solution is to add a
typesconditional export, as you will read in the documentation linked above.