Configuring vite plus with nuxt

[finleyjb]

The vite plus docs say

Put test configuration directly in the test block in vite.config.ts so all your configuration stays in one place. We do not recommend using vitest.config.ts with Vite+.

The documentation makes it sound like the primary reason for this is just developer ergonomics. Are there any problems a separate vitest config would cause other than having configs in multiple places?

The reason why I'm asking is that nuxt requires that you put vite configuration in a nuxt.config.ts file, while the test configuration should go in a vitest.config.ts file. I'm guessing the nuxt config file also uses the vite version of defineConfig rather than the vite plus version of defineConfig.

What would be the consequences of configuring things like this?

For context, this is used as a monorepo where the root uses vite plus with a package that uses nuxt.

[ZTjack]

@finleyjb I wouldn't try to squeeze the Nuxt package into vite.config.ts. Nuxt still expects a vitest.config.ts using @nuxt/test-utils/config, so it's fine to let that package be the exception.

The Vite+ recommendation is mainly about its built-in vp test command, since that reads the test block from vite.config.ts. For the Nuxt workspace, I'd use a normal package script and run it with vp run test:

{
  "scripts": {
    "test": "vitest"
  }
}

// vitest.config.ts
import { defineVitestConfig } from '@nuxt/test-utils/config'

export default defineVitestConfig({
  test: {
    environment: 'nuxt',
  },
})

That should coexist fine with Vite+ at the monorepo root. This package just won't pick up test settings from the root vite.config.ts, so you'll need to import any shared options yourself. Vite+ documents its config behavior here: https://viteplus.dev/guide/test#configuration. Nuxt's setup is here: https://nuxt.com/docs/3.x/getting-started/testing.

[finleyjb]

Got it. It would be nice if the vite+ docs spelled out the reasoning a little better.