chore(deps): update eslint packages (#9615)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Vladimir Sheremet <sleuths.slews0s@icloud.com>

Author: renovate[bot]

.github/commit-convention.md

@@ -2,7 +2,7 @@
 
 > This is adapted from [Angular's commit convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular).
 
-#### TL;DR:
+### TL;DR:
 
 Messages must be matched by the following regex:
 

README.md

@@ -20,7 +20,7 @@ Vitest
 Next generation testing framework powered by Vite.
 <p>
 <p align="center">
-  <a href="https://npmx.dev/package/vitest"><img src="https://img.shields.io/npm/v/vitest?color=729B1B&label="></a>
+  <a href="https://npmx.dev/package/vitest"><img src="https://img.shields.io/npm/v/vitest?color=729B1B&label=" alt="current vitest version badge"></a>
 <p>
 
 <p align="center">
@@ -89,31 +89,31 @@ $ npx vitest
 
 <p align="center">
   <a href="https://cdn.jsdelivr.net/gh/sheremet-va/static/vitest/sponsors.svg">
-    <img src='https://cdn.jsdelivr.net/gh/sheremet-va/static/vitest/sponsors.svg'/>
+    <img src='https://cdn.jsdelivr.net/gh/sheremet-va/static/vitest/sponsors.svg' alt="vitest's sponsors"/>
   </a>
 </p>
 
 ### Vladimir Sponsors
 
 <p align="center">
   <a href="https://cdn.jsdelivr.net/gh/sheremet-va/static/sponsors.svg">
-    <img src='https://cdn.jsdelivr.net/gh/sheremet-va/static/sponsors.svg'/>
+    <img src='https://cdn.jsdelivr.net/gh/sheremet-va/static/sponsors.svg' alt="vladimir's sponsors"/>
   </a>
 </p>
 
 ### Anthony Fu Sponsors
 
 <p align="center">
   <a href="https://cdn.jsdelivr.net/gh/antfu/static/sponsors.svg">
-    <img src='https://cdn.jsdelivr.net/gh/antfu/static/sponsors.svg'/>
+    <img src='https://cdn.jsdelivr.net/gh/antfu/static/sponsors.svg' alt="anthony's sponsors"/>
   </a>
 </p>
 
 ### Patak Sponsors
 
 <p align="center">
   <a href="https://cdn.jsdelivr.net/gh/patak-dev/static/sponsors.svg">
-    <img src='https://cdn.jsdelivr.net/gh/patak-dev/static/sponsors.svg'/>
+    <img src='https://cdn.jsdelivr.net/gh/patak-dev/static/sponsors.svg' alt="patak's sponsors"/>
   </a>
 </p>
 

docs/api/advanced/test-project.md

@@ -51,7 +51,7 @@ export default defineConfig({
 :::
 
 ::: info
-If the [root project](/api/advanced/vitest#getroottestproject) is not part of user projects, its `name` will not be resolved.
+If the [root project](/api/advanced/vitest#getrootproject) is not part of user projects, its `name` will not be resolved.
 :::
 
 ## vitest
@@ -78,7 +78,7 @@ project.serializedConfig === project.serializedConfig // ❌
 
 ## globalConfig
 
-The test config that [`Vitest`](/api/advanced/vitest) was initialized with. If this is the [root project](/api/advanced/vitest#getroottestproject), `globalConfig` and `config` will reference the same object. This config is useful for values that cannot be set on the project level, like `coverage` or `reporters`.
+The test config that [`Vitest`](/api/advanced/vitest) was initialized with. If this is the [root project](/api/advanced/vitest#getrootproject), `globalConfig` and `config` will reference the same object. This config is useful for values that cannot be set on the project level, like `coverage` or `reporters`.
 
 ```ts
 import type { ResolvedConfig } from 'vitest/node'
@@ -206,7 +206,7 @@ Also note that `project.createSpecification` always returns a new instance.
 function isRootProject(): boolean
 ```
 
-Checks if the current project is the root project. You can also get the root project by calling [`vitest.getRootProject()`](#getrootproject).
+Checks if the current project is the root project. You can also get the root project by calling [`vitest.getRootProject()`](/api/advanced/vitest#getrootproject).
 
 ## globTestFiles
 

docs/api/browser/locators.md

@@ -65,7 +65,7 @@ By default, many semantic elements in HTML have a role; for example, `<input typ
 Providing roles via `role` or `aria-*` attributes to built-in elements that already have an implicit role is **highly discouraged** by ARIA guidelines.
 :::
 
-##### Options
+**Options**
 
 - `exact: boolean`
 
@@ -189,7 +189,7 @@ Providing roles via `role` or `aria-*` attributes to built-in elements that alre
   page.getByRole('button', { selected: false }) // ❌
   ```
 
-##### See also
+**See also**
 
 - [List of ARIA roles at MDN](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles)
 - [List of ARIA roles at w3.org](https://www.w3.org/TR/wai-aria-1.2/#role_definitions)
@@ -213,13 +213,13 @@ page.getByAltText(/incredibles.*? poster/i) // ✅
 page.getByAltText('non existing alt text') // ❌
 ```
 
-#### Options
+**Options**
 
 - `exact: boolean`
 
   Whether the `text` is matched exactly: case-sensitive and whole-string. Disabled by default. This option is ignored if `text` is a regular expression. Note that exact match still trims whitespace.
 
-#### See also
+**See also**
 
 - [testing-library's `ByAltText`](https://testing-library.com/docs/queries/byalttext/)
 
@@ -260,13 +260,13 @@ The `page.getByLabelText('Username')` locator will find every input in the examp
 <input aria-label="Username" />
 ```
 
-#### Options
+**Options**
 
 - `exact: boolean`
 
   Whether the `text` is matched exactly: case-sensitive and whole-string. Disabled by default. This option is ignored if `text` is a regular expression. Note that exact match still trims whitespace.
 
-#### See also
+**See also**
 
 - [testing-library's `ByLabelText`](https://testing-library.com/docs/queries/bylabeltext/)
 
@@ -292,13 +292,13 @@ page.getByPlaceholder('not found') // ❌
 It is generally better to rely on a label using [`getByLabelText`](#getbylabeltext) than a placeholder.
 :::
 
-#### Options
+**Options**
 
 - `exact: boolean`
 
   Whether the `text` is matched exactly: case-sensitive and whole-string. Disabled by default. This option is ignored if `text` is a regular expression. Note that exact match still trims whitespace.
 
-#### See also
+**See also**
 
 - [testing-library's `ByPlaceholderText`](https://testing-library.com/docs/queries/byplaceholdertext/)
 
@@ -324,13 +324,13 @@ page.getByText('about', { exact: true }) // ❌
 This locator is useful for locating non-interactive elements. If you need to locate an interactive element, like a button or an input, prefer [`getByRole`](#getbyrole).
 :::
 
-#### Options
+**Options**
 
 - `exact: boolean`
 
   Whether the `text` is matched exactly: case-sensitive and whole-string. Disabled by default. This option is ignored if `text` is a regular expression. Note that exact match still trims whitespace.
 
-#### See also
+**See also**
 
 - [testing-library's `ByText`](https://testing-library.com/docs/queries/bytext/)
 
@@ -352,13 +352,13 @@ page.getByTitle('Delete') // ✅
 page.getByTitle('Create') // ❌
 ```
 
-#### Options
+**Options**
 
 - `exact: boolean`
 
   Whether the `text` is matched exactly: case-sensitive and whole-string. Disabled by default. This option is ignored if `text` is a regular expression. Note that exact match still trims whitespace.
 
-#### See also
+**See also**
 
 - [testing-library's `ByTitle`](https://testing-library.com/docs/queries/bytitle/)
 
@@ -381,13 +381,13 @@ page.getByTestId('non-existing-element') // ❌
 It is recommended to use this only after the other locators don't work for your use case. Using `data-testid` attributes does not resemble how your software is used and should be avoided if possible.
 :::
 
-#### Options
+**Options**
 
 - `exact: boolean`
 
   Whether the `text` is matched exactly: case-sensitive and whole-string. Disabled by default. This option is ignored if `text` is a regular expression. Note that exact match still trims whitespace.
 
-#### See also
+**See also**
 
 - [testing-library's `ByTestId`](https://testing-library.com/docs/queries/bytestid/)
 

docs/api/expect.md

@@ -6,7 +6,7 @@ The following types are used in the type signatures below
 type Awaitable<T> = T | PromiseLike<T>
 ```
 
-`expect` is used to create assertions. In this context `assertions` are functions that can be called to assert a statement. Vitest provides `chai` assertions by default and also `Jest` compatible assertions built on top of `chai`. Since Vitest 4.1, for spy/mock testing, Vitest also provides [Chai-style assertions](#chai-style-spy-assertions) (e.g., `expect(spy).to.have.been.called()`) alongside Jest-style assertions (e.g., `expect(spy).toHaveBeenCalled()`). Unlike `Jest`, Vitest supports a message as the second argument - if the assertion fails, the error message will be equal to it.
+`expect` is used to create assertions. In this context `assertions` are functions that can be called to assert a statement. Vitest provides `chai` assertions by default and also `Jest` compatible assertions built on top of `chai`. Since Vitest 4.1, for spy/mock testing, Vitest also provides Chai-style assertions (e.g., [`expect(spy).to.have.been.called()`](#called)) alongside Jest-style assertions (e.g., `expect(spy).toHaveBeenCalled()`). Unlike `Jest`, Vitest supports a message as the second argument - if the assertion fails, the error message will be equal to it.
 
 ```ts
 export interface ExpectStatic extends Chai.ExpectStatic, AsymmetricMatchersContaining {

docs/blog/vitest-3-2.md

@@ -47,7 +47,7 @@ This option will be removed completely in a future major, replaced by `projects`
 
 The new [annotation API](/guide/test-annotations) allows you to annotate any test with a custom message and attachment. These annotations are visible in the UI, HTML, junit, tap and GitHub Actions reporters. Vitest will also print related annotation in the CLI if the test fails.
 
-<img src="/annotation-api-cute-puppy-example.png" />
+<img src="/annotation-api-cute-puppy-example.png" alt="an example of annotation with a cute puppy" />
 
 ## Scoped Fixtures
 
@@ -106,7 +106,7 @@ export default defineConfig({
 ```
 :::
 
-<img src="/v3-2-custom-colors.png" />
+<img src="/v3-2-custom-colors.png" alt="an example of project names with custom backgrounds" />
 
 ## Custom Browser Locators API
 

docs/blog/vitest-3.md

@@ -67,7 +67,7 @@ Alongside this change, we also redesign the public reporter API (the `reporters`
 You can follow the design process in [#7069](https://github.com/vitest-dev/vitest/pull/7069) PR. It was a hard fight trying to reverse-engineer the previous `onTaskUpdate` API to make this new elegant lifecycle possible.
 
 <div class="flex align-center justify-center">
-  <img src="/on-task-update.gif" />
+  <img src="/on-task-update.gif" alt="a gif from it's always sunny with a drawing board" />
 </div>
 
 ## Inline Workspace

docs/config/alias.md

@@ -12,7 +12,7 @@ Define custom aliases when running inside tests. They will be merged with aliase
 ::: warning
 Vitest uses Vite SSR primitives to run tests which has [certain pitfalls](https://vitejs.dev/guide/ssr.html#ssr-externals).
 
-1. Aliases affect only modules imported directly with an `import` keyword by an [inlined](#server-deps-inline) module (all source code is inlined by default).
+1. Aliases affect only modules imported directly with an `import` keyword by an [inlined](/config/server#server-deps-inline) module (all source code is inlined by default).
 2. Vitest does not support aliasing `require` calls.
 3. If you are aliasing an external dependency (e.g., `react` -> `preact`), you may want to alias the actual `node_modules` packages instead to make it work for externalized dependencies. Both [Yarn](https://classic.yarnpkg.com/en/docs/cli/add/#toc-yarn-add-alias) and [pnpm](https://pnpm.io/aliases/) support aliasing via the `npm:` prefix.
 :::

docs/config/benchmark.md

@@ -28,7 +28,7 @@ Exclude globs for benchmark test files
 - **Type:** `string[]`
 - **Default:** `[]`
 
-Include globs for in-source benchmark test files. This option is similar to [`includeSource`](#includesource).
+Include globs for in-source benchmark test files. This option is similar to [`includeSource`](/config/include-source).
 
 When defined, Vitest will run all matched files with `import.meta.vitest` inside.
 

docs/config/browser/api.md

@@ -9,7 +9,7 @@ outline: deep
 - **Default:** `63315`
 - **CLI:** `--browser.api=63315`, `--browser.api.port=1234, --browser.api.host=example.com`
 
-Configure options for Vite server that serves code in the browser. Does not affect [`test.api`](#api) option. By default, Vitest assigns port `63315` to avoid conflicts with the development server, allowing you to run both in parallel.
+Configure options for Vite server that serves code in the browser. Does not affect [`test.api`](/config/api) option. By default, Vitest assigns port `63315` to avoid conflicts with the development server, allowing you to run both in parallel.
 
 ## api.allowWrite <Version>4.1.0</Version> {#api-allowwrite}