From version Node v8.9.0, require.resolve() accepts custom paths about resolve-from HOT 7 OPEN

Awesome to see this finally being added to core.

from resolve-from.

I tried this out using require.resolve with the paths option but couldn't make it work given this structure:

unicorn
    node_modules
        foo.js
    bar
        cat.js
index.js

const path = require('path');

require.resolve('foo', {paths: [path.join(__dirname, 'unicorn', 'bar')]});

I'd expect it to use the regular module resolution and just traverse upwards. Works fine if I run it without the paths option from cat.js.

from resolve-from.

It should be

const path = require('path');

require.resolve('foo', {
  paths: require.resolve.paths(path.join(__dirname, 'unicorn', 'bar'))
})

from resolve-from.

It should work anyway if it follows the usual module resolution which the documentation states it does. Anyway, it doesn't work using your example either.

from resolve-from.

require.resolve doesn't work with custom paths (no idea why), but this module works fine

from resolve-from.

but it can't work with exports access the esm entry

from resolve-from.

Now that NodeJS have paths option built in, then i suppose that there is no point in upgrading this pkg to ESM and we could just deprecate this package and say something like: just use native function, here is how...

from resolve-from.