@vitest-agent/mcp 1.0.1 → 1.2.0

package/public/vendor/vitest-docs/config/coverage.md

@@ -1,455 +0,0 @@
-# coverage <CRoot /> {#coverage}
-
-You can use [`v8`](/guide/coverage.html#v8-provider), [`istanbul`](/guide/coverage.html#istanbul-provider) or [a custom coverage solution](/guide/coverage#custom-coverage-provider) for coverage collection.
-
-You can provide coverage options to CLI with dot notation:
-
-```sh
-npx vitest --coverage.enabled --coverage.provider=istanbul
-```
-
-::: warning
-If you are using coverage options with dot notation, don't forget to specify `--coverage.enabled`. Do not provide a single `--coverage` option in that case.
-:::
-
-## coverage.provider
-
-- **Type:** `'v8' | 'istanbul' | 'custom'`
-- **Default:** `'v8'`
-- **CLI:** `--coverage.provider=<provider>`
-
-Use `provider` to select the tool for coverage collection.
-
-## coverage.enabled
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.enabled`, `--coverage.enabled=false`
-
-Enables coverage collection. Can be overridden using `--coverage` CLI option.
-
-## coverage.include
-
-- **Type:** `string[]`
-- **Default:** Files that were imported during test run
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.include=<pattern>`, `--coverage.include=<pattern1> --coverage.include=<pattern2>`
-
-List of files included in coverage as glob patterns. By default only files covered by tests are included.
-
-It is recommended to pass file extensions in the pattern.
-
-See [Including and excluding files from coverage report](/guide/coverage.html#including-and-excluding-files-from-coverage-report) for examples.
-
-## coverage.exclude
-
-- **Type:** `string[]`
-- **Default:** : `[]`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.exclude=<path>`, `--coverage.exclude=<path1> --coverage.exclude=<path2>`
-
-List of files excluded from coverage as glob patterns.
-
-See [Including and excluding files from coverage report](/guide/coverage.html#including-and-excluding-files-from-coverage-report) for examples.
-
-## coverage.clean
-
-- **Type:** `boolean`
-- **Default:** `true`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.clean`, `--coverage.clean=false`
-
-Clean coverage results before running tests.
-
-## coverage.cleanOnRerun
-
-- **Type:** `boolean`
-- **Default:** `true`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.cleanOnRerun`, `--coverage.cleanOnRerun=false`
-
-Clean coverage report on watch rerun. Set to `false` to preserve coverage results from previous run in watch mode.
-
-## coverage.reportsDirectory
-
-- **Type:** `string`
-- **Default:** `'./coverage'`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.reportsDirectory=<path>`
-
-::: warning
-Vitest will delete this directory before running tests if `coverage.clean` is enabled (default value).
-:::
-
-Directory to write coverage report to.
-
-## coverage.reporter
-
-- **Type:** `string | string[] | [string, {}][]`
-- **Default:** `['text', 'html', 'clover', 'json']`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.reporter=<reporter>`, `--coverage.reporter=<reporter1> --coverage.reporter=<reporter2>`
-
-Coverage reporters to use. See [istanbul documentation](https://istanbul.js.org/docs/advanced/alternative-reporters/) for detailed list of all reporters. See [`@types/istanbul-reports`](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/276d95e4304b3670eaf6e8e5a7ea9e265a14e338/types/istanbul-reports/index.d.ts) for details about reporter specific options.
-
-The reporter has three different types:
-
-- A single reporter: `{ reporter: 'html' }`
-- Multiple reporters without options: `{ reporter: ['html', 'json'] }`
-- A single or multiple reporters with reporter options:
-  <!-- eslint-skip -->
-  ```ts
-  {
-    reporter: [
-      ['lcov', { 'projectRoot': './src' }],
-      ['json', { 'file': 'coverage.json' }],
-      ['text']
-    ]
-  }
-  ```
-
-You can also pass custom coverage reporters. See [Guide - Custom Coverage Reporter](/guide/coverage#custom-coverage-reporter) for more information.
-
-<!-- eslint-skip -->
-```ts
-  {
-    reporter: [
-      // Specify reporter using name of the NPM package
-      '@vitest/custom-coverage-reporter',
-      ['@vitest/custom-coverage-reporter', { someOption: true }],
-
-      // Specify reporter using local path
-      '/absolute/path/to/custom-reporter.cjs',
-      ['/absolute/path/to/custom-reporter.cjs', { someOption: true }],
-    ]
-  }
-```
-
-You can check your coverage report in Vitest UI: check [Vitest UI Coverage](/guide/coverage#vitest-ui) for more details.
-
-::: tip AI coding agents
-When Vitest detects it is running inside an AI coding agent, it automatically adds the `text-summary` reporter and sets `skipFull: true` on the `text` reporter to reduce output and minimize token usage.
-:::
-
-## coverage.reportOnFailure {#coverage-reportonfailure}
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.reportOnFailure`, `--coverage.reportOnFailure=false`
-
-Generate coverage report even when tests fail.
-
-## coverage.allowExternal
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.allowExternal`, `--coverage.allowExternal=false`
-
-Collect coverage of files outside the [project `root`](/config/root).
-
-## coverage.excludeAfterRemap
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.excludeAfterRemap`, `--coverage.excludeAfterRemap=false`
-
-Apply exclusions again after coverage has been remapped to original sources.
-This is useful when your source files are transpiled and may contain source maps of non-source files.
-
-Use this option when you are seeing files that show up in report even if they match your `coverage.exclude` patterns.
-
-## coverage.skipFull
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.skipFull`, `--coverage.skipFull=false`
-
-Do not show files with 100% statement, branch, and function coverage.
-
-## coverage.thresholds
-
-Options for coverage thresholds.
-
-If a threshold is set to a positive number, it will be interpreted as the minimum percentage of coverage required. For example, setting the lines threshold to `90` means that 90% of lines must be covered.
-
-If a threshold is set to a negative number, it will be treated as the maximum number of uncovered items allowed. For example, setting the lines threshold to `-10` means that no more than 10 lines may be uncovered.
-
-<!-- eslint-skip -->
-```ts
-{
-  coverage: {
-    thresholds: {
-      // Requires 90% function coverage
-      functions: 90,
-
-      // Require that no more than 10 lines are uncovered
-      lines: -10,
-    }
-  }
-}
-```
-
-### coverage.thresholds.lines
-
-- **Type:** `number`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.thresholds.lines=<number>`
-
-Global threshold for lines.
-
-### coverage.thresholds.functions
-
-- **Type:** `number`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.thresholds.functions=<number>`
-
-Global threshold for functions.
-
-### coverage.thresholds.branches
-
-- **Type:** `number`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.thresholds.branches=<number>`
-
-Global threshold for branches.
-
-### coverage.thresholds.statements
-
-- **Type:** `number`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.thresholds.statements=<number>`
-
-Global threshold for statements.
-
-### coverage.thresholds.perFile
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.thresholds.perFile`, `--coverage.thresholds.perFile=false`
-
-Check thresholds per file.
-
-### coverage.thresholds.autoUpdate
-
-- **Type:** `boolean | function`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.thresholds.autoUpdate=<boolean>`
-
-Update all threshold values `lines`, `functions`, `branches` and `statements` to configuration file when current coverage is better than the configured thresholds.
-This option helps to maintain thresholds when coverage is improved.
-
-You can also pass a function for formatting the updated threshold values:
-
-<!-- eslint-skip -->
-```ts
-{
-  coverage: {
-    thresholds: {
-      // Update thresholds without decimals
-      autoUpdate: (newThreshold) => Math.floor(newThreshold),
-
-      // 95.85 -> 95
-      functions: 95,
-    }
-  }
-}
-```
-
-### coverage.thresholds.100
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.thresholds.100`, `--coverage.thresholds.100=false`
-
-Sets global thresholds to 100.
-Shortcut for `--coverage.thresholds.lines 100 --coverage.thresholds.functions 100 --coverage.thresholds.branches 100 --coverage.thresholds.statements 100`.
-
-### coverage.thresholds[glob-pattern]
-
-- **Type:** `{ statements?: number functions?: number branches?: number lines?: number }`
-- **Default:** `undefined`
-- **Available for providers:** `'v8' | 'istanbul'`
-
-Sets thresholds for files matching the glob pattern.
-
-::: tip NOTE
-Vitest counts all files, including those covered by glob-patterns, into the global coverage thresholds.
-This is different from Jest behavior.
-:::
-
-<!-- eslint-skip -->
-```ts
-{
-  coverage: {
-    thresholds: {
-      // Thresholds for all files
-      functions: 95,
-      branches: 70,
-
-      // Thresholds for matching glob pattern
-      'src/utils/**.ts': {
-        statements: 95,
-        functions: 90,
-        branches: 85,
-        lines: 80,
-      },
-
-      // Files matching this pattern will only have lines thresholds set.
-      // Global thresholds are not inherited.
-      '**/math.ts': {
-        lines: 100,
-      }
-    }
-  }
-}
-```
-
-### coverage.thresholds[glob-pattern].100
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **Available for providers:** `'v8' | 'istanbul'`
-
-Sets thresholds to 100 for files matching the glob pattern.
-
-<!-- eslint-skip -->
-```ts
-{
-  coverage: {
-    thresholds: {
-      // Thresholds for all files
-      functions: 95,
-      branches: 70,
-
-      // Thresholds for matching glob pattern
-      'src/utils/**.ts': { 100: true },
-      '**/math.ts': { 100: true }
-    }
-  }
-}
-```
-
-## coverage.ignoreClassMethods
-
-- **Type:** `string[]`
-- **Default:** `[]`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.ignoreClassMethods=<method>`
-
-Set to array of class method names to ignore for coverage.
-See [istanbul documentation](https://github.com/istanbuljs/nyc#ignoring-methods) for more information.
-
-## coverage.watermarks
-
-- **Type:**
-<!-- eslint-skip -->
-```ts
-{
-  statements?: [number, number],
-  functions?: [number, number],
-  branches?: [number, number],
-  lines?: [number, number]
-}
-```
-
-- **Default:**
-<!-- eslint-skip -->
-```ts
-{
-  statements: [50, 80],
-  functions: [50, 80],
-  branches: [50, 80],
-  lines: [50, 80]
-}
-```
-
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.watermarks.statements=50,80`, `--coverage.watermarks.branches=50,80`
-
-Watermarks for statements, lines, branches and functions. See [istanbul documentation](https://github.com/istanbuljs/nyc#high-and-low-watermarks) for more information.
-
-## coverage.processingConcurrency
-
-- **Type:** `boolean`
-- **Default:** `Math.min(20, os.availableParallelism?.() ?? os.cpus().length)`
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.processingConcurrency=<number>`
-
-Concurrency limit used when processing the coverage results.
-
-## coverage.instrumenter <Version type="experimental">4.1.5</Version> {#coverage-instrumenter}
-
-- **Type:** `(options: InstrumenterOptions) => CoverageInstrumenter`
-- **Available for providers:** `'istanbul'`
-
-Factory for a custom instrumenter to use in place of the default `istanbul-lib-instrument`. Vitest calls the factory once during initialization and reuses the returned instrumenter for every file. The rest of the Istanbul pipeline (collection, merging, reporting) is unchanged.
-
-The factory receives an `InstrumenterOptions` object with Vitest's runtime coverage settings, and must return an object implementing the `CoverageInstrumenter` interface. Both types are exported from `vitest/node`.
-
-<!-- eslint-skip -->
-```ts
-interface InstrumenterOptions {
-  coverageVariable: string
-  coverageGlobalScope: string
-  coverageGlobalScopeFunc: boolean
-  ignoreClassMethods: string[]
-}
-
-interface CoverageInstrumenter {
-  instrumentSync: (code: string, filename: string, inputSourceMap?: any) => string
-  lastSourceMap: () => any
-  lastFileCoverage: () => any
-}
-```
-
-<!-- eslint-skip -->
-```ts
-import { defineConfig } from 'vitest/config'
-import { createInstrumenter } from '@vitest/some-custom-instrumenter'
-
-export default defineConfig({
-  test: {
-    coverage: {
-      provider: 'istanbul',
-      instrumenter: options => createInstrumenter(options),
-    }
-  }
-})
-```
-
-## coverage.customProviderModule
-
-- **Type:** `string`
-- **Available for providers:** `'custom'`
-- **CLI:** `--coverage.customProviderModule=<path or module name>`
-
-Specifies the module name or path for the custom coverage provider module. See [Guide - Custom Coverage Provider](/guide/coverage#custom-coverage-provider) for more information.
-
-## coverage.htmlDir
-
-- **Type:** `string`
-- **Default:** Automatically inferred from `html`, `html-spa`, or `lcov` coverage reporters
-- **CLI:** `--coverage.htmlDir=<path>`
-
-Directory of HTML coverage output to be served in [Vitest UI](/guide/ui) and [HTML reporter](/guide/reporters.html#html-reporter).
-
-This is automatically configured when using builtin coverage reporters that produce HTML output (`html`, `html-spa`, and `lcov`). Use this option to override with a custom coverage reporting location when using custom coverage reporters.
-
-Note that setting this option does not change where coverage HTML report is generated. Configure the `coverage.reporter` option to change the directory instead.
-
-## coverage.changed
-
-- **Type:** `boolean | string`
-- **Default:** `false` (inherits from `test.changed`)
-- **Available for providers:** `'v8' | 'istanbul'`
-- **CLI:** `--coverage.changed`, `--coverage.changed=<commit/branch>`
-
-Collect coverage only for files changed since a specified commit or branch. When set to `true`, it uses staged and unstaged changes.

package/public/vendor/vitest-docs/config/css.md

@@ -1,47 +0,0 @@
-# css
-
-- **Type:** `boolean | { include?, exclude?, modules? }`
-
-Configure if CSS should be processed. When excluded, CSS files will be replaced with empty strings to bypass the subsequent processing. CSS Modules will return a proxy to not affect runtime.
-
-::: warning
-This option is not applied to [browser tests](/guide/browser/).
-:::
-
-## css.include
-
-- **Type:** `RegExp | RegExp[]`
-- **Default:** `[]`
-
-RegExp pattern for files that should return actual CSS and will be processed by Vite pipeline.
-
-:::tip
-To process all CSS files, use `/.+/`.
-:::
-
-## css.exclude
-
-- **Type:** `RegExp | RegExp[]`
-- **Default:** `[]`
-
-RegExp pattern for files that will return an empty CSS file.
-
-## css.modules
-
-- **Type:** `{ classNameStrategy? }`
-- **Default:** `{}`
-
-### css.modules.classNameStrategy
-
-- **Type:** `'stable' | 'scoped' | 'non-scoped'`
-- **Default:** `'stable'`
-
-If you decide to process CSS files, you can configure if class names inside CSS modules should be scoped. You can choose one of the options:
-
-- `stable`: class names will be generated as `_${name}_${hashedFilename}`, which means that generated class will stay the same, if CSS content is changed, but will change, if the name of the file is modified, or file is moved to another folder. This setting is useful, if you use snapshot feature.
-- `scoped`: class names will be generated as usual, respecting `css.modules.generateScopedName` method, if you have one and CSS processing is enabled. By default, filename will be generated as `_${name}_${hash}`, where hash includes filename and content of the file.
-- `non-scoped`: class names will not be hashed.
-
-::: warning
-By default, Vitest exports a proxy, bypassing CSS Modules processing. If you rely on CSS properties on your classes, you have to enable CSS processing using `include` option.
-:::

package/public/vendor/vitest-docs/config/dangerouslyignoreunhandlederrors.md

@@ -1,23 +0,0 @@
-# dangerouslyIgnoreUnhandledErrors <CRoot />
-
-- **Type:** `boolean`
-- **Default:** `false`
-- **CLI:**
-  - `--dangerouslyIgnoreUnhandledErrors`
-  - `--dangerouslyIgnoreUnhandledErrors=false`
-
-If this option is set to `true`, Vitest will not fail the test run if there are unhandled errors. Note that built-in reporters will still report them.
-
-If you want to filter out certain errors conditionally, use [`onUnhandledError`](/config/onunhandlederror) callback instead.
-
-## Example
-
-```js [vitest.config.js]
-import { defineConfig } from 'vitest/config'
-
-export default defineConfig({
-  test: {
-    dangerouslyIgnoreUnhandledErrors: true,
-  },
-})
-```

package/public/vendor/vitest-docs/config/deps.md

@@ -1,127 +0,0 @@
-# deps
-
-- **Type:** `{ optimizer?, ... }`
-
-Handling for dependencies resolution.
-
-## deps.optimizer {#deps-optimizer}
-
-- **Type:** `{ ssr?, client? }`
-- **See also:** [Dep Optimization Options](https://vitejs.dev/config/dep-optimization-options.html)
-
-Enable dependency optimization. If you have a lot of tests, this might improve their performance.
-
-When Vitest encounters the external library listed in `include`, it will be bundled into a single file using esbuild and imported as a whole module. This is good for several reasons:
-
-- Importing packages with a lot of imports is expensive. By bundling them into one file we can save a lot of time
-- Importing UI libraries is expensive because they are not meant to run inside Node.js
-- Your `alias` configuration is now respected inside bundled packages
-- Code in your tests is running closer to how it's running in the browser
-
-Be aware that only packages in `deps.optimizer?.[mode].include` option are bundled (some plugins populate this automatically, like Svelte). You can read more about available options in [Vite](https://vitejs.dev/config/dep-optimization-options.html) docs (Vitest doesn't support `disable` and `noDiscovery` options). By default, Vitest uses `optimizer.client` for `jsdom` and `happy-dom` environments, and `optimizer.ssr` for `node` and `edge` environments.
-
-This options also inherits your `optimizeDeps` configuration (for web Vitest will extend `optimizeDeps`, for ssr - `ssr.optimizeDeps`). If you redefine `include`/`exclude` option in `deps.optimizer` it will extend your `optimizeDeps` when running tests. Vitest automatically removes the same options from `include`, if they are listed in `exclude`.
-
-::: tip
-You will not be able to edit your `node_modules` code for debugging, since the code is actually located in your `cacheDir` or `test.cache.dir` directory. If you want to debug with `console.log` statements, edit it directly or force rebundling with `deps.optimizer?.[mode].force` option.
-:::
-
-### deps.optimizer.{mode}.enabled
-
-- **Type:** `boolean`
-- **Default:** `false`
-
-Enable dependency optimization.
-
-## deps.client  {#deps-client}
-
-- **Type:** `{ transformAssets?, ... }`
-
-Options that are applied to external files when the environment is set to `client`. By default, `jsdom` and `happy-dom` use `client` environment, while `node` and `edge` environments use `ssr`, so these options will have no affect on files inside those environments.
-
-Usually, files inside `node_modules` are externalized, but these options also affect files in [`server.deps.external`](/config/server#server-deps-external).
-
-### deps.client.transformAssets
-
-- **Type:** `boolean`
-- **Default:** `true`
-
-Should Vitest process assets (.png, .svg, .jpg, etc) files and resolve them like Vite does in the browser.
-
-This module will have a default export equal to the path to the asset, if no query is specified.
-
-::: warning
-At the moment, this option only works with [`vmThreads`](/config/pool#vmthreads) and [`vmForks`](/config/pool#vmforks) pools.
-:::
-
-### deps.client.transformCss
-
-- **Type:** `boolean`
-- **Default:** `true`
-
-Should Vitest process CSS (.css, .scss, .sass, etc) files and resolve them like Vite does in the browser.
-
-If CSS files are disabled with [`css`](/config/css) options, this option will just silence `ERR_UNKNOWN_FILE_EXTENSION` errors.
-
-::: warning
-At the moment, this option only works with [`vmThreads`](/config/pool#vmthreads) and [`vmForks`](/config/pool#vmforks) pools.
-:::
-
-### deps.client.transformGlobPattern
-
-- **Type:** `RegExp | RegExp[]`
-- **Default:** `[]`
-
-Regexp pattern to match external files that should be transformed.
-
-By default, files inside `node_modules` are externalized and not transformed, unless it's CSS or an asset, and corresponding option is not disabled.
-
-::: warning
-At the moment, this option only works with [`vmThreads`](/config/pool#vmthreads) and [`vmForks`](/config/pool#vmforks) pools.
-:::
-
-## deps.interopDefault
-
-- **Type:** `boolean`
-- **Default:** `true`
-
-Interpret CJS module's default as named exports. Some dependencies only bundle CJS modules and don't use named exports that Node.js can statically analyze when a package is imported using `import` syntax instead of `require`. When importing such dependencies in Node environment using named exports, you will see this error:
-
-```
-import { read } from 'fs-jetpack';
-         ^^^^
-SyntaxError: Named export 'read' not found. The requested module 'fs-jetpack' is a CommonJS module, which may not support all module.exports as named exports.
-CommonJS modules can always be imported via the default export.
-```
-
-Vitest doesn't do static analysis, and cannot fail before your running code, so you will most likely see this error when running tests, if this feature is disabled:
-
-```
-TypeError: createAsyncThunk is not a function
-TypeError: default is not a function
-```
-
-By default, Vitest assumes you are using a bundler to bypass this and will not fail, but you can disable this behaviour manually, if your code is not processed.
-
-## deps.moduleDirectories
-
-- **Type:** `string[]`
-- **Default:** `['node_modules']`
-
-A list of directories that should be treated as module directories. This config option affects the behavior of [`vi.mock`](/api/vi#vi-mock): when no factory is provided and the path of what you are mocking matches one of the `moduleDirectories` values, Vitest will try to resolve the mock by looking for a `__mocks__` folder in the [root](/config/root) of the project.
-
-This option will also affect if a file should be treated as a module when externalizing dependencies. By default, Vitest imports external modules with native Node.js bypassing Vite transformation step.
-
-Setting this option will _override_ the default, if you wish to still search `node_modules` for packages include it along with any other options:
-
-```ts
-import { defineConfig } from 'vitest/config'
-
-export default defineConfig({
-  test: {
-    deps: {
-      moduleDirectories: ['node_modules', path.resolve('../../packages')],
-    }
-  },
-})
-```

package/public/vendor/vitest-docs/config/detectasyncleaks.md

@@ -1,39 +0,0 @@
-# detectAsyncLeaks
-
-- **Type:** `boolean`
-- **CLI:** `--detectAsyncLeaks`, `--detect-async-leaks`
-- **Default:** `false`
-
-::: warning
-Enabling this option will make your tests run much slower. Use only when debugging or developing tests.
-:::
-
-Detect asynchronous resources leaking from the test file.
-Uses [`node:async_hooks`](https://nodejs.org/api/async_hooks.html) to track creation of async resources. If a resource is not cleaned up, it will be logged after tests have finished.
-
-For example if your code has `setTimeout` calls that execute the callback after tests have finished, you will see following error:
-
-```sh
-⎯⎯⎯⎯⎯⎯⎯⎯ Async Leaks 1 ⎯⎯⎯⎯⎯⎯⎯⎯
-
-Timeout leaking in test/checkout-screen.test.tsx
- 26|
- 27|   useEffect(() => {
- 28|     setTimeout(() => setWindowWidth(window.innerWidth), 150)
-   |     ^
- 29|   })
- 30|
-```
-
-To fix this, you'll need to make sure your code cleans the timeout properly:
-
-```js
-useEffect(() => {
-  setTimeout(() => setWindowWidth(window.innerWidth), 150) // [!code --]
-  const timeout = setTimeout(() => setWindowWidth(window.innerWidth), 150) // [!code ++]
-
-  return function cleanup() { // [!code ++]
-    clearTimeout(timeout) // [!code ++]
-  } // [!code ++]
-})
-```