chore(deps-dev): update eslint requirement from ^8.56.0 to ^8.57.0 #1067
dependabot[bot]Annotations
13 errors and 1 warning
|
src/layers/deck.gl/VLayerDeckArc.vue#L2
Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)
|
|
src/layers/deck.gl/VLayerDeckArc.vue#L4
Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)
|
|
src/layers/deck.gl/VLayerDeckArc.vue#L19
Unexpected any. Specify a different type (@typescript-eslint/no-explicit-any)
|
|
src/layers/deck.gl/VLayerDeckGeojson.vue#L2
Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)
|
|
src/layers/deck.gl/VLayerDeckGeojson.vue#L4
Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)
|
|
src/layers/deck.gl/VLayerDeckGeojson.vue#L6
Unable to resolve path to module 'geojson' (import/no-unresolved)
|
|
src/map/VMap.vue#L14
Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)
|
|
test/setup/index.ts#L4
Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)
|
|
test/setup/index.ts#L7
Use "@ts-expect-error" instead of "@ts-ignore", as "@ts-ignore" will do nothing if the following line is error-free (@typescript-eslint/ban-ts-comment)
|
|
vite-env.d.ts#L5
Don't use `{}` as a type. `{}` actually means "any non-nullish value".
- 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.
- If you want a type meaning "empty object", you probably want `Record<string, never>` instead.
- If you really want a type meaning "any non-nullish value", you probably want `NonNullable<unknown>` instead (@typescript-eslint/ban-types)
|
|
vite-env.d.ts#L5
Don't use `{}` as a type. `{}` actually means "any non-nullish value".
- 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.
- If you want a type meaning "empty object", you probably want `Record<string, never>` instead.
- If you really want a type meaning "any non-nullish value", you probably want `NonNullable<unknown>` instead (@typescript-eslint/ban-types)
|
|
vite-env.d.ts#L5
Unexpected any. Specify a different type (@typescript-eslint/no-explicit-any)
|
|
CI / CI
Linting failures detected. See check runs with annotations for details.
|
|
CI / CI
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: wearerequired/lint-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|