# eslint-plugin-vitest > Eslint plugin for vitest Latest version **0.5.4** (published 2024-04-23) · MIT license · 0 weekly downloads > **Better alternative:** See documentation for alternatives (https://github.com/AikidoSec/module-replacements/blob/main/docs/eslint-plugin-vitest) ## Install ```sh npm install eslint-plugin-vitest pnpm add eslint-plugin-vitest yarn add eslint-plugin-vitest bun add eslint-plugin-vitest ``` ## Health **Score 45/100 (D)** — status: abandoned. Positive: has types; esm support; no vulnerabilities; high maintenance score; high quality score. Warnings: low downloads; pre 1.0. Negative: abandoned. ## Facts | | | |---|---| | Version | 0.5.4 | | Published | 2024-04-23 | | First published | 2022-01-02 | | Weekly downloads | 0 | | License | MIT | | TypeScript types | bundled | | Module format | ESM + CommonJS | | Node | ^18.0.0 \|\| >= 20.0.0 | | Dependencies | 1 | | Unpacked size | 383.2 KB | | Known vulnerabilities | 0 | | Install scripts | no | | GitHub stars | 509 | | Author | Verite Mugabo Makuza | | Maintainers | veritem | | Keywords | eslint, eslintplugin, eslint-plugin, vitest eslint plugin, vitest, eslint plugin | ## Links - npm: https://www.npmjs.com/package/eslint-plugin-vitest - Repository: https://github.com/veritem/eslint-plugin-vitest - Homepage: https://github.com/veritem/eslint-plugin-vitest#readme - Issues: https://github.com/veritem/eslint-plugin-vitest/issues - npm.io page: https://npm.io/package/eslint-plugin-vitest ## Dependencies (1) - [@typescript-eslint/utils](https://npm.io/package/@typescript-eslint/utils.md) ^7.7.1 ## Alternatives - [eslint-plugin-sonarjs](https://npm.io/package/eslint-plugin-sonarjs.md) — 2.9M weekly downloads - [eslint-config-expo](https://npm.io/package/eslint-config-expo.md) — 1.5M weekly downloads - [@matter/protocol](https://npm.io/package/@matter/protocol.md) — 63.5K weekly downloads - [@eventcatalog/linter](https://npm.io/package/@eventcatalog/linter.md) — 24.8K weekly downloads - [@inrupt/eslint-config-base](https://npm.io/package/@inrupt/eslint-config-base.md) — 4.5K weekly downloads ## Recent versions - 0.5.4 (latest) — 2024-04-23 - 0.5.3 — 2024-04-14 - 0.5.2 — 2024-04-13 - 0.5.1 — 2024-04-09 - 0.5.0 — 2024-04-09 - 0.4.2-beta.5 — 2024-04-08 - 0.4.2-beta.3 — 2024-04-06 - 0.4.2-beta.2 — 2024-04-06 - 0.4.2-beta.1 — 2024-04-05 - 0.4.1 — 2024-03-31 - 0.4.0 — 2024-03-25 - 0.3.26 — 2024-03-12 - 0.3.25 — 2024-03-11 - 0.3.24 — 2024-03-08 - 0.3.23 — 2024-03-08 - … 81 more at https://npm.io/package/eslint-plugin-vitest/versions ## README ## eslint-plugin-vitest ![npm](https://img.shields.io/npm/v/eslint-plugin-vitest) [![ci](https://github.com/veritem/eslint-plugin-vitest/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/veritem/eslint-plugin-vitest/actions/workflows/ci.yml) Eslint plugin for vitest ### Installation You'll first need to install [ESLint](https://eslint.org/): ```sh npm i eslint --save-dev ``` Next, install `eslint-plugin-vitest`: ```sh npm install eslint-plugin-vitest --save-dev ``` ### Usage Make sure you're running eslint `v9.0.0` or higher for the latest version of this plugin to work. The following example is how your `eslint.config.js` should be setup for this plugin to work for you. ```js import vitest from "eslint-plugin-vitest"; export default [ { files: ["tests/**"], // or any other pattern plugins: { vitest }, rules: { ...vitest.configs.recommended.rules, // you can also use vitest.configs.all.rules to enable all rules "vitest/max-nested-describe": ["error", { "max": 3 }] // you can also modify rules' behavior using option like this }, }, ]; ``` If you're not using the latest version of eslint (version `v8.57.0` or lower) you can setup this plugin using the following configuration Add `vitest` to the plugins section of your `.eslintrc` configuration file. You can omit the `eslint-plugin-` prefix: ```json { "plugins": ["vitest"] } ``` Then configure the rules you want to use under the rules section. ```json { "rules": { "vitest/max-nested-describe": [ "error", { "max": 3 } ] } } ``` #### Enabling with type-testing Vitest ships with an optional [type-testing feature](https://vitest.dev/guide/testing-types), which is disabled by default. If you're using this feature, you should also enabled `typecheck` in the settings for this plugin. This ensures that rules like [expect-expect](docs/rules/expect-expect.md) account for type-related assertions in tests. ```js import vitest from "eslint-plugin-vitest"; export default [ { files: ["tests/**"], // or any other pattern plugins: { vitest, }, rules: { ...vitest.configs.recommended.rules, }, settings: { vitest: { typecheck: true } }, languageOptions: { globals: { ...vitest.environments.env.globals, }, }, }, ] ``` ### Rules 💼 Configurations enabled in.\ ⚠️ Configurations set to warn in.\ 🌐 Set in the `all` configuration.\ ✅ Set in the `recommended` configuration.\ 🔧 Automatically fixable by the [`--fix` CLI option](https://eslint.org/docs/user-guide/command-line-interface#--fix).\ 💡 Manually fixable by [editor suggestions](https://eslint.org/docs/latest/use/core-concepts#rule-suggestions).\ ❌ Deprecated. | Name                                                | Description | 💼 | ⚠️ | 🔧 | 💡 | ❌ | | :----------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------- | :- | :- | :- | :- | :- | | [consistent-test-filename](docs/rules/consistent-test-filename.md) | require .spec test file pattern | | 🌐 | | | | | [consistent-test-it](docs/rules/consistent-test-it.md) | enforce using test or it but not both | | 🌐 | 🔧 | | | | [expect-expect](docs/rules/expect-expect.md) | enforce having expectation in test body | ✅ | | | | | | [max-expects](docs/rules/max-expects.md) | enforce a maximum number of expect per test | | 🌐 | | | | | [max-nested-describe](docs/rules/max-nested-describe.md) | require describe block to be less than set max value or default value | | 🌐 | | | | | [no-alias-methods](docs/rules/no-alias-methods.md) | disallow alias methods | | 🌐 | 🔧 | | | | [no-commented-out-tests](docs/rules/no-commented-out-tests.md) | disallow commented out tests | ✅ | | | | | | [no-conditional-expect](docs/rules/no-conditional-expect.md) | disallow conditional expects | | 🌐 | | | | | [no-conditional-in-test](docs/rules/no-conditional-in-test.md) | disallow conditional tests | | 🌐 | | | | | [no-conditional-tests](docs/rules/no-conditional-tests.md) | disallow conditional tests | | 🌐 | | | | | [no-disabled-tests](docs/rules/no-disabled-tests.md) | disallow disabled tests | | 🌐 | | | | | [no-done-callback](docs/rules/no-done-callback.md) | disallow using a callback in asynchronous tests and hooks | | 🌐 | | 💡 | ❌ | | [no-duplicate-hooks](docs/rules/no-duplicate-hooks.md) | disallow duplicate hooks and teardown hooks | | 🌐 | | | | | [no-focused-tests](docs/rules/no-focused-tests.md) | disallow focused tests | | 🌐 | 🔧 | | | | [no-hooks](docs/rules/no-hooks.md) | disallow setup and teardown hooks | | 🌐 | | | | | [no-identical-title](docs/rules/no-identical-title.md) | disallow identical titles | ✅ | | 🔧 | | | | [no-import-node-test](docs/rules/no-import-node-test.md) | disallow importing `node:test` | ✅ | | 🔧 | | | | [no-interpolation-in-snapshots](docs/rules/no-interpolation-in-snapshots.md) | disallow string interpolation in snapshots | | 🌐 | 🔧 | | | | [no-large-snapshots](docs/rules/no-large-snapshots.md) | disallow large snapshots | | 🌐 | | | | | [no-mocks-import](docs/rules/no-mocks-import.md) | disallow importing from __mocks__ directory | | 🌐 | | | | | [no-restricted-matchers](docs/rules/no-restricted-matchers.md) | disallow the use of certain matchers | | 🌐 | | | | | [no-restricted-vi-methods](docs/rules/no-restricted-vi-methods.md) | disallow specific `vi.` methods | | 🌐 | | | | | [no-standalone-expect](docs/rules/no-standalone-expect.md) | disallow using `expect` outside of `it` or `test` blocks | | 🌐 | | | | | [no-test-prefixes](docs/rules/no-test-prefixes.md) | disallow using `test` as a prefix | | 🌐 | 🔧 | | | | [no-test-return-statement](docs/rules/no-test-return-statement.md) | disallow return statements in tests | | 🌐 | | | | | [prefer-called-with](docs/rules/prefer-called-with.md) | enforce using `toBeCalledWith()` or `toHaveBeenCalledWith()` | | 🌐 | 🔧 | | | | [prefer-comparison-matcher](docs/rules/prefer-comparison-matcher.md) | enforce using the built-in comparison matchers | | 🌐 | 🔧 | | | | [prefer-each](docs/rules/prefer-each.md) | enforce using `each` rather than manual loops | | 🌐 | | | | | [prefer-equality-matcher](docs/rules/prefer-equality-matcher.md) | enforce using the built-in quality matchers | | 🌐 | | 💡 | | | [prefer-expect-assertions](docs/rules/prefer-expect-assertions.md) | enforce using expect assertions instead of callbacks | | 🌐 | | 💡 | | | [prefer-expect-resolves](docs/rules/prefer-expect-resolves.md) | enforce using `expect().resolves` over `expect(await ...)` syntax | | 🌐 | 🔧 | | | | [prefer-hooks-in-order](docs/rules/prefer-hooks-in-order.md) | enforce having hooks in consistent order | | 🌐 | | | | | [prefer-hooks-on-top](docs/rules/prefer-hooks-on-top.md) | enforce having hooks before any test cases | | 🌐 | | | | | [prefer-lowercase-title](docs/rules/prefer-lowercase-title.md) | enforce lowercase titles | | 🌐 | 🔧 | | | | [prefer-mock-promise-shorthand](docs/rules/prefer-mock-promise-shorthand.md) | enforce mock resolved/rejected shorthands for promises | | 🌐 | 🔧 | | | | [prefer-snapshot-hint](docs/rules/prefer-snapshot-hint.md) | enforce including a hint with external snapshots | | 🌐 | | | | | [prefer-spy-on](docs/rules/prefer-spy-on.md) | enforce using `vi.spyOn` | | 🌐 | 🔧 | | | | [prefer-strict-equal](docs/rules/prefer-strict-equal.md) | enforce strict equal over equal | | 🌐 | | 💡 | | | [prefer-to-be](docs/rules/prefer-to-be.md) | enforce using toBe() | | 🌐 | 🔧 | | | | [prefer-to-be-falsy](docs/rules/prefer-to-be-falsy.md) | enforce using toBeFalsy() | | 🌐 | 🔧 | | | | [prefer-to-be-object](docs/rules/prefer-to-be-object.md) | enforce using toBeObject() | | 🌐 | 🔧 | | | | [prefer-to-be-truthy](docs/rules/prefer-to-be-truthy.md) | enforce using `toBeTruthy` | | 🌐 | 🔧 | | | | [prefer-to-contain](docs/rules/prefer-to-contain.md) | enforce using toContain() | | 🌐 | 🔧 | | | | [prefer-to-have-length](docs/rules/prefer-to-have-length.md) | enforce using toHaveLength() | | 🌐 | 🔧 | | | | [prefer-todo](docs/rules/prefer-todo.md) | enforce using `test.todo` | | 🌐 | 🔧 | | | | [require-hook](docs/rules/require-hook.md) | require setup and teardown to be within a hook | | 🌐 | | | | | [require-local-test-context-for-concurrent-snapshots](docs/rules/require-local-test-context-for-concurrent-snapshots.md) | require local Test Context for concurrent snapshot tests | ✅ | | | | | | [require-to-throw-message](docs/rules/require-to-throw-message.md) | require toThrow() to be called with an error message | | 🌐 | | | | | [require-top-level-describe](docs/rules/require-top-level-describe.md) | enforce that all tests are in a top-level describe | | 🌐 | | | | | [valid-describe-callback](docs/rules/valid-describe-callback.md) | enforce valid describe callback | ✅ | | | | | | [valid-expect](docs/rules/valid-expect.md) | enforce valid `expect()` usage | ✅ | | | | | | [valid-title](docs/rules/valid-title.md) | enforce valid titles | ✅ | | 🔧 | | | #### Credits - [eslint-plugin-jest](https://github.com/jest-community/eslint-plugin-jest) Most of the rules in this plugin are essentially ports of Jest plugin rules with minor modifications ### Licence [MIT](https://github.com/veritem/eslint-plugin-vitest/blob/main/LICENSE) Licence © 2022 - present [veritem](https://github.com/veritem) --- _Source: https://npm.io/package/eslint-plugin-vitest · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._