Vladimir

I am suggesting these: - expect `expect` inside a test - enforce either `test` or `it`, but not both - prefer either `toBeCalled` or `toHaveBeenCalled` (and so on) - prefer...

> We are far from merging this anyway. We need to know that mocking modules work with vitest. And there are spies similar to Jest Mocking interface is the same...

hey, @anncwb can you look at this, when you have time? This is stopping our adoption of Histoire 😄

> * Start a Vitest server and communicate with it Yeah, I think Vitest has an api to communicate with `--ui`? Can you use that? ---- Edit: > They are...

Maybe we can use https://github.com/johnsoncodehk/volar/tree/master/packages/vue-component-meta ?

Hello! I think one of the problems we will encounter, if we were to use esm, is mocking Module methods. As far as I know spec doesn't allow rewriting exported...

To fix some of the described problems we are thinking to add a loader that will only process aliasing inside `node_modules`, and to use our own module resolution for source...

> It is possible with a loader I don't see how it's possible with provided link? It's not possible to redefine property on `Module` object. This is how spying works,...

@antfu can you have a look? 😄

> I think indeed the current behavior is a kinda flaw and the fix makes a lot of sense. As for the shipping, I think we could have the workaround...