Docs: missing info about defineConfig() merging user configs with default configs

[bobaaaaa]

Describe the bug

It is not clear to me if my options for defineConfig() will be merged with the default options. A short info about this would be helpful for me.

Example:

Is this the correct why to add an exclude path for the coverage option?

import { defineConfig, coverageConfigDefaults } from 'vitest/config';

export default defineConfig({
  test: {
    coverage: {
      exclude: [...coverageConfigDefaults.exclude, '**/foo.ts'],
    },
  },
});

I also checked the vite docs about this.

PS: love vitest ❤️

Reproduction

only about docs

System Info

vitest 1.0.0-beta.3

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

I am not sure what you mean. All your options always override default options otherwise it wouldn't be possible to override them.

[bobaaaaa]

I am not sure what you mean. All your options always override default options otherwise it wouldn't be possible to override them.

Ok, I thought so, but it is not clear in the docs to me. This is my first project with vitest. Sorry if this is a stupid question.