Setting vitest environment in package.json doesn't play well with VS Code's vitest extension

[segevfiner]

Setting the vitest environment to jsdom in the package.json instead of in vite.config.ts doesn't play well with the VS Code vitest extension which won't know about it and will fail to run vitest without further configuration.

create-vue/template/config/vitest/package.json

Line 3 in 99775d3

"test:unit": "vitest --environment jsdom --root src/"

[haoqunjiang]

I think this needs to be reported to the Vitest VS Code extension instead of here?

It is a fair use of the CLI arguments considering how few options the command needs to use. The VS Code extension should support this use case.

[segevfiner]

How would it know which script it should look at? There is probably a VS Code setting to set which CLI arguments should be used, but that's not as good as it just working without further configuration.

[haoqunjiang]

I think they can use some heuristics to suggest a setting.

But yeah, your argument makes sense. It is not ideal.
I need to figure out a way to make it work out of the box without sacrificing simplicity.

[segevfiner]

Isn't just setting it in vite.config.ts simple enough?

[haoqunjiang]

I kinda don't like using /// <reference types="vitest" />, so I'm looking into the documentation, trying to find a different way now. If there turn out to be no better options, I'll use it then.

[segevfiner]

BTW, Seems like this had another unfortunate side effect, vitest in VS Code didn't know about the root flag so it would also pick up playwright tests.

[haoqunjiang]

Yeah, the --root src/ argument was initially introduced to work around that problem.

Anyway, thanks to @beta, now we'll create a perfectly working and scalable vitest.config.js file for new projects: https://github.com/vuejs/create-vue/pull/227/files