5 ms·

Vitest, fast unit-test framework powered by Vite

yladiz 5y ago
I'm curious what others think about this: I feel like a lot of tools written like this (Vite, Vitest) are written for Vue specifically, and while of course there are reasons for building new tools that are more Vue focused, it feels like a lot of them are built partly because of not-invented-here. I haven't been on top of the ecosystem changes so much lately, so I might be off base, but do others feel like this too? Am I missing something?
- hiimshort 5y ago
  I've used Vite for a handful of projects now and have been quite impressed. My projects use Preact and associated tech which I haven't had problems with in Vite. There are some teething issues still with tooling integrations like Storybook, but I'm hopeful they'll improve. In fact, Vitest fills quite the void already. Testing applications built with Vite was a bit annoying since you had to wire up Jest to use Vite. Lots of redundancy in that toolchain, making Vitest a welcome replacement. I do agree that a lot of this technology is being developed out of a need from the Vue developers and community. That's not at all a bad thing. Vue's cli UI (oxymoronic, huh) is still lightyears ahead of any other offering. I'm amazed that it's been some 4 years and nobody has replicated it in popular projects. Though, what I do appreciate with Vite (and tools like Vitest) is that while they were built from a need of the Vue community, it is architected to be largely (or entirely) framework agnostic. Preact and React work great on Vite.
- rk06 5y ago
  Vite is framework agnsotic. i.e. there are no special hacks or features for Vue. the API and internals are on the same level for all js frameworks. So while Vue does get more benefit out of it, because original core team is also core vue team, other framework author can leverage Vite as much as Vue is leveraging it. For the record, Solid, svelte and others have adopted vite, and are actively using it. Angular can't adopt vite as easily because of the decisions taken by angular team. ------------- On NIH syndrome, this is while technically true, it is justified here. The cause of NIH is esmodules, which are relatively new. Hence, old tech is being re-written or updated to leverage esmodules. Vite is one example of it. Vitest which uses vite is another example of it.

I'm curious what others think about this: I feel like a lot of tools written like this (Vite, Vitest) are written for Vue specifically, and while of course there are reasons for building new tools that are more Vue focused, it feels like a lot of them are built partly because of not-invented-here. I haven't been on top of the ecosystem changes so much lately, so I might be off base, but do others feel like this too? Am I missing something?

hiimshort 5y ago
I've used Vite for a handful of projects now and have been quite impressed. My projects use Preact and associated tech which I haven't had problems with in Vite. There are some teething issues still with tooling integrations like Storybook, but I'm hopeful they'll improve. In fact, Vitest fills quite the void already. Testing applications built with Vite was a bit annoying since you had to wire up Jest to use Vite. Lots of redundancy in that toolchain, making Vitest a welcome replacement. I do agree that a lot of this technology is being developed out of a need from the Vue developers and community. That's not at all a bad thing. Vue's cli UI (oxymoronic, huh) is still lightyears ahead of any other offering. I'm amazed that it's been some 4 years and nobody has replicated it in popular projects. Though, what I do appreciate with Vite (and tools like Vitest) is that while they were built from a need of the Vue community, it is architected to be largely (or entirely) framework agnostic. Preact and React work great on Vite.
rk06 5y ago
Vite is framework agnsotic. i.e. there are no special hacks or features for Vue. the API and internals are on the same level for all js frameworks. So while Vue does get more benefit out of it, because original core team is also core vue team, other framework author can leverage Vite as much as Vue is leveraging it. For the record, Solid, svelte and others have adopted vite, and are actively using it. Angular can't adopt vite as easily because of the decisions taken by angular team. ------------- On NIH syndrome, this is while technically true, it is justified here. The cause of NIH is esmodules, which are relatively new. Hence, old tech is being re-written or updated to leverage esmodules. Vite is one example of it. Vitest which uses vite is another example of it.