Support for jest.mock() about babel-plugin-module-resolver HOT 7 CLOSED

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?

from babel-plugin-module-resolver.

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?

from babel-plugin-module-resolver.

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

from babel-plugin-module-resolver.

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

from babel-plugin-module-resolver.

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?

from babel-plugin-module-resolver.

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

from babel-plugin-module-resolver.

Sure (#126)

from babel-plugin-module-resolver.