Make vitest a peer dependency or expose vitest bin

[tobiasdiez]

Currently, nuxt-vitest declares vitest as a dependency. However, it is not possible to invoke binaries exposed by transitive dependencies (at least for yarn, see yarnpkg/berry#1875). Thus users are forced to install vitest as well, so that you end up with two versions of vitest which might lead to version mismatches and issues such as https://github.com/danielroe/nuxt-vitest/issues/132.

Proposal:

• Either make vitest a peer dependency
• Re-expose the vitest binary in nuxt-vitest

[danielroe]

I think it would make sense for vitest to be a peerDep.

[danielroe]

resolved in danielroe/nuxt-vitest@616b721.

[marr]

Thanks for this @danielroe - I just realized that the dep is a bit restrictive due to vitest still being prerelease (<1). Should the version be something like ~0 to support all pre-release versions of vitest? Currently if you $ ni -D @nuxt/test-utils nuxt-vitest on a fresh nuxt install, this will fail.