Expose mocks directly with `mockNuxtImport`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 437
- Forks
- 120
- Avg merge
- 22h 52m
- Merged PRs (30d)
- 23
Description
Currently, it's possible to mock a Nuxt import:
mockNuxtImport('useStorage', () => {
return vi.fn()
})
When we want to access this mock in our test, to run an assertion or to change the implementation, we can use vi.hoisted:
const { useStorageMock } = vi.hoisted(() => {
return {
useStorageMock: vi.fn()
}
})
mockNuxtImport('useStorage', () => {
return useStorageMock
})
// now we can change the implementation of useStorageMock between tests
This is a lot of code just to define and expose a single mock. Would it be possible to make mocking Nuxt imports easier by returning the mocks directly in mockNuxtImport?
I propose something like this:
const useStorageMock = mockNuxtImport('useStorage', () => {
return vi.fn()
})
// now we can change the implementation of useStorageMock between tests
I'm down to have a look at this if this is possible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the mockNuxtImport entry point and trace how the mock factory is registered. Check the existing testing utilities and verify that the returned mock can be asserted on and reconfigured between tests; done means the proposed direct-return usage works without vi.hoisted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100