docs: fix fakeTimers migration example and remove // (#7458)

Author: sheremet-va

docs/.vitepress/config.ts

@@ -31,6 +31,10 @@ export default ({ mode }: { mode: string }) => {
     lang: 'en-US',
     title: vitestName,
     description: vitestDescription,
+    srcExclude: [
+      '**/guide/examples/*',
+      '**/guide/cli-generated.md',
+    ],
     locales: {
       root: {
         label: 'English',

docs/guide/examples/promise-done.md

@@ -0,0 +1,8 @@
+```js
+it('should work', (done) => {  // [!code --]
+it('should work', () => new Promise(done => { // [!code ++]
+  // ...
+  done()
+}) // [!code --]
+})) // [!code ++]
+```

docs/guide/migration.md

@@ -69,8 +69,8 @@ foo.bar() // 'Hello, mock!'
 
 foo.bar.mockReset()
 
-foo.bar() // undefined // [!code --]
-foo.bar() // 'Hello, world!' // [!code ++]
+foo.bar() // undefined [!code --]
+foo.bar() // 'Hello, world!' [!code ++]
 ```
 
 ### `vi.spyOn` Reuses Mock if Method is Already Mocked
@@ -81,8 +81,8 @@ Previously, Vitest would always assign a new spy when spying on an object. This
 vi.spyOn(fooService, 'foo').mockImplementation(() => 'bar')
 vi.spyOn(fooService, 'foo').mockImplementation(() => 'bar')
 vi.restoreAllMocks()
-vi.isMockFunction(fooService.foo) // true // [!code --]
-vi.isMockFunction(fooService.foo) // false // [!code ++]
+vi.isMockFunction(fooService.foo) // true [!code --]
+vi.isMockFunction(fooService.foo) // false [!code ++]
 ```
 
 ### Fake Timers Defaults
@@ -92,8 +92,8 @@ Vitest no longer provides default `fakeTimers.toFake` options. Now, Vitest will
 ```ts
 vi.useFakeTimers()
 
-performance.now() // original // [!code --]
-performance.now() // fake // [!code ++]
+performance.now() // original [!code --]
+performance.now() // fake [!code ++]
 ```
 
 You can revert to the previous behaviour by specifying timers when calling `vi.useFakeTimers` or globally in the config:
@@ -102,7 +102,15 @@ You can revert to the previous behaviour by specifying timers when calling `vi.u
 export default defineConfig({
   test: {
     fakeTimers: {
-      toFake: ['setTimeout', 'clearTimeout', 'Date'], // [!code ++]
+      toFake: [ // [!code ++]
+        'setTimeout', // [!code ++]
+        'clearTimeout', // [!code ++]
+        'setInterval', // [!code ++]
+        'clearInterval', // [!code ++]
+        'setImmediate', // [!code ++]
+        'clearImmediate', // [!code ++]
+        'Date', // [!code ++]
+      ] // [!code ++]
     },
   },
 })
@@ -278,8 +286,8 @@ Previously Vitest resolved `mock.results` values if the function returned a Prom
 const fn = vi.fn().mockResolvedValueOnce('result')
 await fn()
 
-const result = fn.mock.results[0] // 'result' // [!code --]
-const result = fn.mock.results[0] // 'Promise<result>' // [!code ++]
+const result = fn.mock.results[0] // 'result' [!code --]
+const result = fn.mock.results[0] // 'Promise<result>' [!code ++]
 
 const settledResult = fn.mock.settledResults[0] // 'result'
 ```
@@ -530,14 +538,7 @@ If you want to modify the object, you will use [replaceProperty API](https://jes
 
 From Vitest v0.10.0, the callback style of declaring tests is deprecated. You can rewrite them to use `async`/`await` functions, or use Promise to mimic the callback style.
 
-```
-it('should work', (done) => {  // [!code --]
-it('should work', () => new Promise(done => { // [!code ++]
-  // ...
-  done()
-}) // [!code --]
-})) // [!code ++]
-```
+<!--@include: ./examples/promise-done.md-->
 
 ### Hooks
 

eslint.config.js

@@ -30,6 +30,7 @@ export default antfu(
       'docs/guide/snapshot.md',
       // uses invalid js example
       'docs/advanced/api/import-example.md',
+      'docs/guide/examples/*.md',
     ],
   },
   {