Beyond just finding a module's absolute path, how can the `require.resolve.paths()` method be used for debugging module resolution issues in a complex project?
Node.js interview question for Advanced practice.
Answer
require.resolve.paths(request) is a lesser-known but powerful debugging tool that returns an array of the paths that Node.js will search when attempting to resolve the given request string. This differs from require.resolve() which only returns the final resolved path or throws an error. Practical Application for Debugging: In a complex project with a nested directory structure or a monorepo, you might be surprised where Node.js is looking for a module. If a require('my-shared-lib') call is failing, you can add console.log(require.resolve.paths('my-shared-lib')); to your code right before the failing require. This will output an array of all the nodemodules directories Node will check, starting from the current file's directory and moving up to the root. This allows you to see the exact search paths and instantly diagnose why your module isn't being found (e.g., it's not in any of the searched locations, or a typo exists in a directory name).
Explanation
require.resolve.paths() will return an array of paths even if the module is not ultimately found, whereas require.resolve() will throw an error in that case.