chore(deps-dev): bump @typescript-eslint/eslint-plugin from 7.18.0 to 8.14.0 #4180
Annotations
4 errors and 1 warning
example/src/vite-env.d.ts#L1
Definition for rule '@typescript-eslint/ban-types' was not found (@typescript-eslint/ban-types)
|
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)
|
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)
|
CI
Linting failures detected. See check runs with annotations for details.
|
CI
The following actions use a deprecated Node.js version and will be forced to run on node20: wearerequired/lint-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|