Open Source preparing

[antfu]

We aim to public Vitest when we reached v0.0.100

Pre tasks

• [x] Emphasis on the working in progress warning
• [x] Add WIP warning banner in docs
• [x] Remove sponsor message and note
• [x] Discourage for migrating from Jest or other tools ATM
  • We can say "You can give a Vitest try for new projects, but migrating from other testing tools is not recommended at the current stage."
• [x] Add collaborators avatar in docs
• [x] #203
• [x] #208
• [x] #220

Post tasks

• [x] Move to vitest-dev org
• [x] Enable CI
• [x] Update vitest.dev to the docs
• [x] Announcement on Twitter (could be delayed for a while to make sure everything working)
• [x] Apply for Netlify org

[patak-dev]

I don't see opened Windows issues, @antfu are there other issues you are aware of? @userquin, things are looking good for you after your last fix, no?

[userquin]

I think we have all cases covered since it is handle and centralized on execute.ts module, ts-starter used for cjs but I think we should also test it on esm from external/real project, maybe using sveltekit.

@antfu also changes all path usages to pathe also including error on lint when using path.

So, we can keep here Fix windows bugs :crossed_fingers: ...

[patak-dev]

Loving pathe, maybe we should use it Vite too. I didn't get your last line @userquin, we should mark it as done, no?

[userquin]

Keep it open for a while, I think you can open vitest with this guy open, we need more feedback from the community... we are using local testing and we should test on real projects... Anyway, let Anthony close it if necessary, but I think there is no need.

[patak-dev]

Ok, checked, for now, the collaborators one has a PR and I don't know if it is really needed for opening it up. I think we are done with the pre-tasks now