Resolution from directories specified via nodePaths ignore package.json exports entries

[clydin]

Currently it is not possible to correctly resolve packages that use the exports field and are located in a directory specified by the nodePaths option. Entries within the exports field appear to be ignored in this case but main fields present will be resolved. This can result in either a resolution failure due to no main fields being present or an incorrect resolution due to a main field being used instead of an exports entry based on the active conditions.

Would it be possible to change the nodePaths resolution from using only loadAsFileOrDirectory to the full node_modules resolution process? This should allow full resolution of packages in alternative node modules directories.