when to use vi.hoisted

-1

I got two difference cases when using vitest to write mocks:

case 1:

const mockedMethod = vi.fn();
vi.mock('./path/to/module.js', () => ({
  originalMethod: mockedMethod,
}));

case 2:

const mockedMethod = [1, 2, 3]; // Defined before vi.mock()
vi.mock('./path/to/module.js', () => ({
  originalMethod: mockedMethod,
}));

I wonder why for case 1, it will raise error to say mockedMethod is undefined. But for case 2, it will pass.

edited Apr 23 at 1:47

Basheer Jarrah

6664 silver badges16 bronze badges

asked Apr 22 at 3:14

hiveer

7678 silver badges17 bronze badges

The question lacks stackoverflow.com/help/mcve , it's unknown what's the context for these cases and whether it's a single case with changed implementation or different ones. mockedMethod is accessed at the time when mocked module is imported. Since vi.mock is hoisted, any values it relies on should be wrapped with vi.hoisted in order to avoid such errors. In case this was the question, that's the answer
– Estus Flask
Commented Apr 22 at 9:46
Best to ask this question to the Vitest devs directly, perhaps in a new discussion here.
– José Ramírez
Commented yesterday

Add a comment |

0 Your Answer

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.