chore(deps-dev): bump @typescript-eslint/eslint-plugin from 7.18.0 to 8.16.0 #4055
Triggered via pull request
November 25, 2024 19:18
dependabot[bot]
dependabot[bot]
opened
#2115
Status
Success
Total duration
13s
Artifacts
–
lint-pr.yml
on: pull_request_target
Validate PR title
3s
Write comment if unsigned commits found
3s
Annotations
3 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)
|
|
Write comment if unsigned commits found
Found: 1 total commits
|