-
Problem: If you have the `prefer-expect-assertions` rule enabled, and also have test like the following...
```JavaScript
it('my test description, ({ expect }) => {
const a = 1;
const b = 2;
…
-
the eslint plugin `eslint-plugin-oxlint` does not parse the `rules.rs`.
Instead it looks recursivly into the rules directory and getting all informations (category: correctness, style, .., plugin-nam…
-
### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
When using `"code_actions_on_format"` in `.ts`, or `.tsx` files only `"source.organizeImports"` ac…
-
I noticed that the current "all" configuration does not apply all the available rules in eslint-plugin-vitest. For example, rules like expect-expect and no-commented-out-tests are not enabled when usi…
-
**Describe the Bug**
The path to `tsconfig.json` in `frontend/.eslintrc.yml` is pointing to `./frontend/tsconfig.json`, so linting typescript files isn't working.
** Steps To Reproduce**
Steps to re…
-
echo -e "foo()\nlet x" > test.js
deno lint test.js
Deno lint finds the unused "x" but it doesn't warn m…
-
**Describe the bug or question**
I've been following the quick start guide without **single-spa Layout Engine** to develop **REACT** application, but I'm getting **Cannot read properties of undefined…
-
This task aims to set up **ESLint** and **Prettier** for the frontend of our monorepo, which is a React-based application. Proper linting and formatting will ensure consistent code quality and styling…
-
Consider this example project, structured similarly to what pnpm produces: [t.tar.gz](https://github.com/user-attachments/files/17951929/t.tar.gz)
The directory structure looks something like this:
`…
-
### Validations
- [X] Follow our [Code of Conduct](https://github.com/eslint-stylistic/eslint-stylistic/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guide](https://eslint.style/contr…