feat(ui): add html coverage

docs/config/index.md

@@ -776,7 +776,7 @@ The reporter has three different types:
   }
   ```
 
-Since Vitest 0.31.0, you can check your coverage report in `Vitest UI`, you only need to add `html` reporter: check [Vitest UI Coverage](/guide/coverage#vitest-ui) for more details.
+Since Vitest 0.31.0, you can check your coverage report in `Vitest UI`: check [Vitest UI Coverage](/guide/coverage#vitest-ui) for more details.
 
 #### coverage.skipFull
 

docs/guide/coverage.md

@@ -166,8 +166,9 @@ To see all configurable options for coverage, see the [coverage Config Reference
 
 ## Vitest UI
 
-Since Vitest 0.31.0, you can check your coverage report in [Vitest UI](./ui), you only need to add `html` reporter.
+Since Vitest 0.31.0, you can check your coverage report in [Vitest UI](./ui).
 
+If you have configured coverage reporters, don't forget to add `html` reporter to the list, Vitest UI will only enable html coverage report if it is present.
 
 <img alt="html coverage activation in Vitest UI" img-light src="/vitest-ui-show-coverage-light.png">
 <img alt="html coverage activation in Vitest UI" img-dark src="/vitest-ui-show-coverage-dark.png">

docs/guide/ui.md

@@ -34,7 +34,7 @@ export default {
 }
 ```
 
-Since Vitest 0.31.0, you can check your coverage report in `Vitest UI`, you only need to add `html` reporter: check [Vitest UI Coverage](/guide/coverage#vitest-ui) for more details.
+Since Vitest 0.31.0, you can check your coverage report in `Vitest UI`: check [Vitest UI Coverage](/guide/coverage#vitest-ui) for more details.
 
 ::: warning
 If you still want to see how your tests are running in real time in the terminal, don't forget to add `default` reporter to `reporters` option: `['default', 'html']`.