when using the config.rootDir jest.setMock doing something unexpected.

[awei01]

There seems to be an issue when using config.rootDir when mocking node_module(s).

folder structure

root
+ client
+ + app
+ + + foo.js
+ + + bar.js
+ + + __tests__
+ + + + test.js
+ node_modules
+ + lodash
+ + kew
+ package.json

root/package.json

{
    "jest":  {
        "rootDir": "client/app"
    }
}

root/client/app/tests/test.js:

'use strict';

describe('using config.rootDir', function() {

    it('has problems when mocking node_modules', function() {

                // lodash and kew have been installed with npm
        jest.setMock('lodash', 'lodash');
        jest.setMock('kew', 'kew');

        console.log(require('lodash'));
        console.log(require('kew'));

    }); 

    it('works when mocking my own modules', function() {

                // ../foo and ../bar are my own modules
        jest.setMock('../foo', 'foo');
        jest.setMock('../bar', 'bar');

        console.log(require('../foo'));
        console.log(require('../bar'));

    });

});

this yields:

Using Jest CLI v0.1.15
Found 1 matching tests...
 PASS  __tests__/baz-test.js (0.032s)
kew
kew
foo
bar
1 tests passed (1 total)
Run time: 0.86s

i was expecting:

Using Jest CLI v0.1.15
Found 1 matching tests...
 PASS  __tests__/baz-test.js (0.032s)
lodash
kew
foo
bar
1 tests passed (1 total)
Run time: 0.86s

[ghost]

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

[cpojer]

I'm going to assume this issue has resolved itself in the last few minor versions.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.