chore(deps-dev): bump @typescript-eslint/eslint-plugin from 7.18.0 to 8.16.0 #2115
GitHub Actions / ESLint
failed
Nov 25, 2024 in 0s
3 errors
ESLint found 3 errors
Annotations
Check failure on line 1 in example/src/vite-env.d.ts
github-actions / ESLint
example/src/vite-env.d.ts#L1
Definition for rule '@typescript-eslint/ban-types' was not found (@typescript-eslint/ban-types)
Check failure on line 7 in example/src/vite-env.d.ts
github-actions / ESLint
example/src/vite-env.d.ts#L7
The `{}` ("empty object") type allows any non-nullish value, including literals like `0` and `""`.
- If that's what you want, disable this lint rule with an inline comment or configure the 'allowObjectTypes' rule option.
- If you want a type meaning "any object", you probably want `object` instead.
- If you want a type meaning "any value", you probably want `unknown` instead (@typescript-eslint/no-empty-object-type)
Check failure on line 7 in example/src/vite-env.d.ts
github-actions / ESLint
example/src/vite-env.d.ts#L7
The `{}` ("empty object") type allows any non-nullish value, including literals like `0` and `""`.
- If that's what you want, disable this lint rule with an inline comment or configure the 'allowObjectTypes' rule option.
- If you want a type meaning "any object", you probably want `object` instead.
- If you want a type meaning "any value", you probably want `unknown` instead (@typescript-eslint/no-empty-object-type)
Loading