fix(babel-plugin-jest-hoist): allow using module wrapper arguments in hoisted mock factory function

[theneva]

Summary

This allows several things. My specific case is using the content of a file as the return value for a mocked function:

jest.mock('some-module', () => {
  const fs = require('fs');
  const path = require('path');

  return {
    someFunction() {
      const pathToHtmlFile = path.resolve(__dirname, 'some-fixture.html');
      const html = fs.readFileSync(pathToHtmlFile);
      return html;
    },
  };
});

The test is located inside a Yarn workspace, and for complicated reasons I have to execute jest from the root of the repository. As far as I can tell, this is the only way I can avoid letting the test know about its own directory path in the repo.

Test plan

To be honest, I'm just doing what @SimenB told me would solve my problem.

I applied this patch to my own repo, and it works. Does it make sense to document this further?

[theneva]

I grouped these with require in the order that the module wrapper passes them

[SimenB]

thanks! just missing a changelog entry 🙂

[github-actions]

This pull request 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.