You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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',()=>{returnuseStorageMock})// 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:
constuseStorageMock=mockNuxtImport('useStorage',()=>{returnvi.fn()})// now we can change the implementation of useStorageMock between tests
I'm down to have a look at this if this is possible.
Hi, I'd like to pick this up. Following the suggested approach, I'll expose the mocks returned from mockNuxtImport so they can be accessed directly in tests, with tests and docs. Could this be assigned to me?
Activity
danielroe commentedon Aug 18, 2023
It seems this should be possible to implement in the same plugin that processes/handles
mockNuxtImport.devsummar commentedon Oct 18, 2026
Hi, I'd like to pick this up. Following the suggested approach, I'll expose the mocks returned from
mockNuxtImportso they can be accessed directly in tests, with tests and docs. Could this be assigned to me?