Enhancement: Support less-opinionated tooling choices about create-vue HOT 4 CLOSED

I was left trying to install Jest myself

You can still install Vitest. Their APIs are quite similar.

In order to make migration easier, the same options from Vue CLI should be allowed

This project is not intended as a guide for migrating from Vue CLI.
So the short answer is no.
I'll elaborate in more detail later if I have time.

But for now, if your project must rely on Jest, I recommend:

• If the use cases can be supported by https://github.com/sodatea/vite-jest/, use it;
• If not, please stay with Vue CLI (use v5 though). It's still maintained. It has a working vue-jest setup.

from create-vue.

A team of chefs picked out the ingredients, designed the APIs, and arranged the order of consumption on your behalf according to their idea of what would make for a tasty full-stack framework. The menu can be both personal and quirky. It isn't designed to appeal to the taste of everyone, everywhere.

from create-vue.

Thanks for the feedback and advice. Since you have refused I will close this. I will try your recommendations.

must rely on Jest

There is nothing wrong with Jest, so I do not want to make unnecessary changes. That is all. It is less framework churn.

A team of chefs picked out the ingredients

I do not like this analogy. Users are the ones doing the cooking. But I understand the point.

from create-vue.

I looked at Vitest previously, and what I found was extremely disappointing since it has recommendation -

Vitest is still in development
It's not recommended to migrate your current testing setups yet

So the Vue website recommends me a project creation tool that provides a not-production-ready unit test driver as the only option. I would say this isn't an issue for the next month or so until the Vue website finishes its migration. After that, I sincerely hope Vitest considers itself to be stable.

from create-vue.