Find modules in additional paths

[eduardoboucas]

I'm trying to make NFT load Node modules from additional paths that aren't necessarily ancestors of the importer's directory. If I understand correctly, the only way to do this currently is to supply a resolve hook, but that means having to rewrite the entire resolving logic.

It'd be great to equip resolvePackage() with the ability to find modules in additional paths, via a configuration property that would work like esbuild's nodePaths property, Webpack's resolve.modules or even the Node's NODE_PATH environment variable.

I'd be happy to submit a PR, but I wanted to first check if you'd be open to it, or whether you have a different recommendation.

Thanks in advance!

[styfle]

@eduardoboucas Sounds like it could be a good feature to match NODE_PATH behavior 👍

How about a new option with a default like the following:

nodePaths = process.env.NODE_PATH.split(';')

nft/src/node-file-trace.ts

Lines 77 to 78 in e89f3ca

	base = process.cwd(),
	processCwd,

@guybedford Any other thoughts to add here?