This is due to TS ignoring the typings top level key when consuming projects use "moduleResolution": "NodeNext" to import from a package with an "exports": {...} entry.
This is unfortunately a fairly high priority merge for us as it is a blocking issue. Tested locally inside of my nodeModules. As an aside, it also works if you delete the exports key, but I believe this is a good thing to have as it is more nuanced and future proof.
This is due to TS ignoring the
typings
top level key when consuming projects use"moduleResolution": "NodeNext"
to import from a package with an"exports": {...}
entry.This is unfortunately a fairly high priority merge for us as it is a blocking issue. Tested locally inside of my nodeModules. As an aside, it also works if you delete the
exports
key, but I believe this is a good thing to have as it is more nuanced and future proof.