Allow overriding the command used to invoke vitest

[coreyward]

Clear and concise description of the problem

I use a script in my package.json to configure various ENV vars and settings when invoking vitest. I would like to configure the extension to use pnpm test to run vitest so my configuration can be shared.

This is basically identical to #366, but despite that issue being closed, there does not appear to be a solution (see below).

I wound up losing my entire development database because I have some tests that verify the database is working correctly using a separate test instance.

Suggested solution

Support a commandLine configuration in the VSCode settings. E.g.,

{
  "vitest.commandLine": "pnpm test"`
}

Alternative

I saw the various other commands like shellType, but they don't appear to be useful for this scenario.

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[sheremet-va]

The extension doesn't use vitest command, it starts a custom node script, so we cannot expose a way to use custom commands. If you need a certain environment, you can use shellType: 'terminal' with a custom vscode terminal setup. You can also setup custom env with vitest.nodeEnv settings option.

[coreyward]

Ah, interesting. I was able to get the nodeEnv to work, but I worry about drift as these commands change. I saw what was in the README re: shellType, but I don't grok how it functions or how to configure it. Are there any examples or additional docs available?

[sheremet-va]

terminal shellType just uses your default vscode terminal. You can configure it using default vscode settings.