eslint-plugin-vitest

eslint-plugin-vitest copied to clipboard

Consider rule for naming mocks created with `vi.fn()`

1

Today I learned about `vi.fn().mockName(...)`. This greatly helps troubleshoot expectations with giving the mock a name. Would you consider adding a rule to check for the absence of `mockName(...)`?

daniel-white

Feature request: `consistent-test-file-path`

2

Some projects nest test files next to relevant source files in several `__tests__` directories. It would be handy to enforce this practice. I found out the hard way that `consistent-test-filename`...

h0adp0re

some rules missing in readme

2

unbound-method and assertion-type are in code and missing in documentation other rules may be missing too

ghost

Add rule `prefer-repeats`

1

Sometimes you want to run a test multiple times. For that reason https://github.com/vitest-dev/vitest/pull/2652 added the `repeats` option. This option should be preferable over `for each number`. This rule is related...

ST-DDT

New rule: `no-only`

1

Essentially [eslint-plugin-no-only-tests](https://www.npmjs.com/package/eslint-plugin-no-only-tests) for vitest, prevent accidentally running `it.only`, `describe.only` etc in CI

GNRSN

Bumps [@typescript-eslint/rule-tester](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/rule-tester) from 8.0.0 to 8.2.0. Release notes Sourced from @​typescript-eslint/rule-tester's releases. v8.2.0 8.2.0 (2024-08-19) 🚀 Features eslint-plugin: add suggestion to require-await to remove async keyword (#9718) typescript-estree: special-case error...

dependabot[bot]

Bumps [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) from 8.0.0 to 8.2.0. Release notes Sourced from @​typescript-eslint/eslint-plugin's releases. v8.2.0 8.2.0 (2024-08-19) 🚀 Features eslint-plugin: add suggestion to require-await to remove async keyword (#9718) typescript-estree: special-case error...

dependabot[bot]

Async `describe` should not be an error

1

`vitest` supports async describe, see https://github.com/vitest-dev/vitest/issues/703#issuecomment-1038925412 and https://github.com/vitest-dev/vitest/pull/750 So this rule should be modified to support `async` https://github.com/vitest-dev/eslint-plugin-vitest/blob/main/docs/rules/valid-describe-callback.md

matyasf

formatting rules are not exported in build output

2

veritem

It seems this is wrongly marked as incorect: ```js expect("foo bar").to.include("foo"); ``` The rule is incorrectly triggered, as this is in fact valid : ``` 6:3 error Expect has unknown...

alexkiro