Update linters (#745) #1637
Annotations
10 warnings
|
pnpm-check:
src/lib/components/LinkWithoutIcon.svelte#L59
Unsafe call of a type that could not be resolved. (@typescript-eslint/no-unsafe-call)
|
|
pnpm-check:
src/lib/components/Link.svelte#L25
Unsafe member access .Mail on a type that cannot be resolved. (@typescript-eslint/no-unsafe-member-access)
|
|
pnpm-check:
src/lib/components/Link.svelte#L23
Unsafe member access .External on a type that cannot be resolved. (@typescript-eslint/no-unsafe-member-access)
|
|
pnpm-check:
src/lib/components/Link.svelte#L19
Unsafe member access .Internal on a type that cannot be resolved. (@typescript-eslint/no-unsafe-member-access)
|
|
pnpm-check:
src/lib/components/LanguageSwitcher.svelte#L182
Use $lib/components/Link.svelte or $lib/components/LinkWithoutIcon.svelte instead (svelte/no-restricted-html-elements)
|
|
pnpm-check:
src/lib/components/LanguageSwitcher.svelte#L168
Use $lib/components/Link.svelte or $lib/components/LinkWithoutIcon.svelte instead (svelte/no-restricted-html-elements)
|
|
pnpm-check:
src/lib/clients/luma/index.ts#L11
Unsafe assignment of an `any` value. (@typescript-eslint/no-unsafe-assignment)
|
|
pnpm-check:
src/lib/clients/luma/index.test.ts#L7
A method that is not declared with `this: void` may cause unintentional scoping of `this` when separated from its object.
Consider using an arrow function or explicitly `.bind()`ing the method to avoid calling the method with an unintended `this` value.
If a function does not access `this`, it can be annotated with `this: void`. (@typescript-eslint/unbound-method)
|
|
pnpm-check:
eslint.config.js#L44
Unsafe member access .replace on an `any` value. (@typescript-eslint/no-unsafe-member-access)
|
|
pnpm-check:
eslint.config.js#L44
Unsafe call of an `any` typed value. (@typescript-eslint/no-unsafe-call)
|