Support for jest.mock()

[sheerun]

Hey,

I have following use-case: I'd like to mock require call with Jest testing framework, but when I do it this way:

file.js

// foobar is rewritten to ../../foobar by this plugin
import foobar from 'foobar'

file.test.js

jest.mock('foobar', () => {
  ...
})

then mock is not instatiated, as foobar is rewritten in tested file by this plugin to ../../foobar

Ideally I would be able to do something like this:

jest.mock(require.resolve('foobar'), () => {
  ...
})

and it would translate to:

jest.mock('../../foobar', () => {
  ...
})

what would result in proper require mocks.

Could this plugin support rewriting also require.resolve(XXX)?

[tleunen]

Not sure to understand what the issue is. You said file.test.js had foobar translated to ../../foobar, which causes an issue. And then you're asking to have require.resolve('foobar') to be translated to ../../foobar. Which is the same thing, right?

[tleunen]

Oh nvm, I misread it.
You're saying the jest test file is not updated with new paths ;)

Hmm.. instead of using require.resolve(), which people won't really use.. Why having a custom syntax for your tests? I'd prefer having a "updateJestMock" option to convert jest.mock(X) to the relative path.

What do you think?

[sheerun]

that might work :) but it's probably issue not only with jest but also other mocking frameworks

[tleunen]

Sure, but I prefer having a custom setting by framework then than having to force people using a different syntax for their tests ;)

[arcanis]

Oh, that's a shame, being able to use require.resolve would have helped me in my case too (I don't use jest, and I use it with a simple readFileSync call which module-resolve probably shouldn't automatically transform) :( If you want to support extra frameworks I can see the reasoning, but shouldn't native functions be supported as well?

[tleunen]

I believe we can also add support for require.resolve. Would you mind creating a new ticket for that?

[arcanis]

Sure (#126)