Starting with typescript v4.7 it can use node16 and nodenext to resolve modules from depending packages. That is it reads the exports field from those packages. With only node as moduleResolution, this exports field is not read and classic resolution is applied.
Now that more and more packages are published with exports field (and drop support for classic/cjs resolving), this needs to be applied. However rollup-plugin-tsignores moduleResolution and thus is not compatible with modern packages.
Expected Behavior
Expected behavior: Use node16/nodenext as default - or even better make it configurable for needs at hand.
tsc
(if applicable): yesStarting with typescript v4.7 it can use
node16
andnodenext
to resolve modules from depending packages. That is it reads theexports
field from those packages. With onlynode
asmoduleResolution
, thisexports
field is not read and classic resolution is applied.Now that more and more packages are published with
exports
field (and drop support for classic/cjs resolving), this needs to be applied. Howeverrollup-plugin-ts
ignoresmoduleResolution
and thus is not compatible with modern packages.Expected Behavior
Expected behavior: Use
node16
/nodenext
as default - or even better make it configurable for needs at hand.Actual Behavior
Ignores
moduleResolution
.