Paths passed to proxyquire must be relative to the file that actually required proxyquire, not to the currently executing test about proxyquire HOT 4 CLOSED

Nope, this is just the way requires work. They're always relative to the file in which they run.

from proxyquire.

@bendrucker I understand that the actual call to require is done in proxyquire, but why would it matter where proxyquire was originally required? The call to proxyquire('../../foo/bar') is in the actual test itself and so I hoped the path would be relative to the test. Thanks for taking the time to explain.

from proxyquire.

Think about this in plain Node terms — what you're basically doing is this:

// a.js
module.exports = require

// b.js
var getModuleViaA = require('./a')
getModuleViaA(/* ... */)

require is a special global that is localized to each module. You can pass it around, but it will always be bound to the module it was created for.

from proxyquire.

As a workaround, you can use module name that has a full absolute path specified, in your calls to proxyquire(...).

from proxyquire.