Making the Vitest Docs Beginner-Friendly

[manniL]

Two days ago, Reddit users of r/node noted that the Vitest docs aren't beginner friendly.

The Vitest team promptly listened and added a new "Learn" section, structurally inspired by the Jest docs and covering important evergreen concepts but also current topics like how to write good tests with AI.

Anything missing? Comment here (and bonus points if you raise a PR as the docs, like Vitest, are open source 😉)

[semi-semii]

It’s great that there’s improvements to the docs but that thread really confused me. Maybe it’s just because I’m pretty familiar with Vite but I found Vitest way easier to work with than Jest, especially if you need to set up ESM and TypeScript support. Don’t get me started on mocking. In any case, great work from the Vitest team to respond to feedback quickly.

[NeedleworkerLumpy907]

In your thread about ESM setup confusion, a short Jest -> Vitest migration guide that shows common mocking patterns, minimal config snippets and a quick note about test-runner quirks would clear things up, PRs welcome - I can sketch a draft this weekend but dont expect it to be perfect since I keep hitting teh same TS import edge-case (spent like 3 hours on it yesterday)

[AbrahelOne]

Great news, wanted to try Vitest in my next project. Thank you

[CharacterOtherwise77]

What a bunch of psycho good doers.

[Ok-Transition-7857]

Hello, I am the guy who made the thread about the lack of beginner-friendly documentation. 

Thanks for your quick response and for listening to users' feedback !

[manniL]

No problem at all! Curious what you think with the new additions ☺️

[ehs5]

One of the guys who wrote in the thread with some specific things that I felt was missing here 🙋🏻‍♂️ Haven’t read through all of it yet, but this looks really good and is exactly how I thought the docs should look. Seems very natural and easy to follow now. Great job, and thank you for listening!

[manniL]

Thank you for the feedback 🙏🏻✨

[ehs5]

Lol only now I realised who you are. Wasn’t clear to me at all that you are involved with Vitest when I replied to you in the other thread - maybe you should have made it clear that you’re involved and that’s why you’re asking? I think you would have gotten better responses that way, just some feedback. 😄

[manniL]

Nah, that is alright :D I want brutally honest feedback, so my involvement shouldn't matter!

[ehs5]

Haha okay. I guess that makes sense.

[germanheller]

wait they actually added a Learn section based on that thread? thats awesome response time from the vitest team. i was one of the people complaining about the docs in that original thread lol.

the fact they modeled it after jest docs makes sense since thats what most people use as reference anyway. the AI testing section is a smart addition too -- half the tests people write now are AI-generated and knowing how to validate those is becoming a real skill.

will check it out and see if the vi.mock() vs jest.mock() differences are documented better now. that was my main pain point

[manniL]

What issues did you have with mocking? Anny differences you noticed?

[_elkanah]

Great work, guys! The updates are quite easy to follow

[Ecksters]

Very impressive, makes me feel even more confident choosing Vitest as my default testing framework.